John,
Thank you very much for your assistance and for teaching me about the dangers of multivalue fields. It seemed like a convenient shortcut originally, and now I know better.
Anyway, I have gotten my many-many relationship working properly and have utilized it in my forms and reports.
There are a few other places where I used multi-value fields. I'm looking to see if I can clean these up.
Within my Projects table, I have fields to define that project, and then a multi-value field for "Related Projects". This field is populated using a combo box with a row source of Projects.ID and Projects.ProjNo. A table linking to itself. (For example, a project might be replacing a motor. A related project would be the work on the item that the motor drives.)
How would I re-create this using a junction table? Potentially:
ID (PK, auto#)
ProjID (PKfrom tProjects)
RelateID (New field within tProjects?)
So on my relationships table, I would have two joins between a pair of tables?
---In MS_Access_Professionals@yahoogroups.com, <JohnV@...> wrote :
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (12) |
Tidak ada komentar:
Posting Komentar