Unanswered: Relationship - 2 manys to 1 one ! How ??
I have been going over this for hours.
I would like for 2 seperate data sets (Sport1 and Sport2) to pull from the same Table (Sports).
Eg Sport1 - Volleyball
Sport2 - Basketball
Ect. . .
I would like Sport1 and Sport2 to pull from Sports
I have tried various methods to do this. .
Making 2 fields Sport1 and Sport2, Then creating a seperate table containing The lists of sports.... but i cant use relationships to tie them together..... after connecting Sport1 > Sports, then attempting to connect Sport2 > Sports, It doesn't allow for 2 relationships. . . I select 'No' >> then it adds a fake table called Sports_1 but the 2 do not update properly.
I am still in a Spreadsheet mindset..... please help me. I love you !
Sport1 << i want values to be restricted to the Sports table [combo box]
Sport2 << same ... restrict to combo box.
I attached a picture of my relationships.
right now i have Combo boxes pointing to Queries that take values from the Sports Table.... when i try to insert Sport1 and Sport2 onto the same form... i usually get a #Name error on one or the other field.
Sometimes.... on the Combo box ... if i tell Sport1 to look at the first row [sportID], then Sport2 to the second row [sport] it seems to work
sorry, i'm going to have to bow out, i don't know combo boxes or anything else in msaccess other than tables and queries
re: capture_07.gif, i can see where the problem is coming from, you've got a rather large table (Title) with 3 slots for sports, and you want to link these via 3 queries to the same table? no idea if you can do that
this may be too late, but can you remove those three columns from Title? create a new table, TitleSport, with columns Sku and SportID, so if a particular Title has three sports, there will be three rows for it in that table... make both Sku and SportID the primary key (a two-column primary key) of TitleSport... have just one Sport table, and then link the TitleSport table to <i>both</i> the Title and Sport tables via the respective columns
The only problem that i can see with what you said is i would like to keep the SKU field a one-to-one relationship to prevent duplicates of sku. Instead... on the report/query end of things i was planning on pulling the values from SportID1, SportID2, and SportID3 to generate information for each sport.
by the way.... in the pictures.... the Sport_1 was generated by Access not me, as well as Producer_1, and Producer_2... do you know what it is doing ?? is it an index/