Search results

IT WORKS!!! Amazing.

I just re-installed it. And the verdict is:

I honestly don't believe that removing ads will fix this issue.

Spam in post #2 reported.

Let us know if you have questions. Be specific!

Yes. It is called an associative or junction table. That is how you implement a many to many relationship. You'll put the junction table's data in your subform(s) as Pat did, with look ups into the other side of the M:M relationship.

Well, did it work?

I answered your question on your other thread. You really don't need to post on the same topic on more than one thread. A possible reason why you haven't had an answer is that your description is a little verbose and doesn't really indicate what you're having problems with. The thing you are...

Please take a look at Pat Hartman's M:M demo: Many-to-many example

I guess if I actually paid to use the sites I use, I wouldn't mind it. I just have a problem with getting free stuff when it wasn't the intention of the person providing the content. Everybody's got to eat.

I recently disabled the Adblock Plus. Maybe that's why this symptom has returned? I'll try re-installing it, I guess. I honestly don't like the idea of Adblock Plus but if it makes the site work correctly, I'll have to bite the bullet.

I don't really understand the issue. Is your combo-box bound to a field in your sub-form's query? If not, it will behave the way you say. Continuous forms are pretty unforgiving about what fields you put on them. Also, I'm a bit confused as to why you need VBA at all. Once the tables are...

Nice. Thanks for the info.

One of the tables on the outside of the M:M relationship goes in the main form. The junction table goes in the sub-form. Using this strategy, you have 2 different ways to see and/or manipulate your data. See Pat Hartman's M:M sample on this site.

All the way. Put things that are about a certain entity in its own entity. I've commented on this multiple times on this forum. For instance, here: http://www.access-programmers.co.uk/forums/showthread.php?t=189081 The purpose of normalization is not as an academic exercise; it is to remove...

Well, 1 problem is that most objects names don't have a space after them and you have added a space after "nama" (at least in the sample you've shown us).

The information shown in the screen shots you sent is not using the code I told you to use in post 12. That code populates the junction table correctly. If it asks for a parameter, see the above paragraph. The old code was not using the correct column names.

Ok, I found several things. Try this: Private Sub Form_AfterInsert() DoCmd.SetWarnings (False) DoCmd.RunSQL "INSERT INTO t_Training_Association ([Employee ID],[Class ID]) select " & Me.txtID & ", [Class ID] from t_Class_Name;" DoCmd.SetWarnings (True) End Sub I ran it on a copy...

What is it doing wrong? It looks like I got the order of columns wrong as I pointed out in my last post. Is there anything else wrong? Still gotta get it trusted and read/write to test it.

Dunno, if you're interested, I can dig through all my old stuff to see if I can find my old disks. It has been a while. Can you deal with floppy disks?