If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Are Primary keys needed in child tables?
Are Primary keys needed in child tables?
How important is having a defined primary key in child tables? Here is my dilemma; I have 35 groups running around come desert country. I having them send updates to a central database with something like XML files (I haven’t exactly figured out how yet). The primary table won’t have any conflicts, but I am contimpated the need to have primary keys in the child tables. Could you guys let me know what you think and if it’s worth combining a group ID with an Auto number in the forms (or if there is some way to have the Jet do it maybe by default?) |
#2
|
|||
|
|||
On Thu, 13 Jan 2005 15:05:06 -0800, "Nevie and Phil"
wrote: Are Primary keys needed in child tables? Primary keys are needed in ALL tables. How important is having a defined primary key in child tables? Essential, if you want to update the table, delete records, sort, .... Here is my dilemma; I have 35 groups running around come desert country. I having them send updates to a central database with something like XML files (I haven’t exactly figured out how yet). The primary table won’t have any conflicts, but I am contimpated the need to have primary keys in the child tables. Could you guys let me know what you think and if it’s worth combining a group ID with an Auto number in the forms (or if there is some way to have the Jet do it maybe by default?) Two suggestions: use a two-field primary key consisting of the groupID and a Long Integer sequential number, probably manually assigned (though an autonumber should work); or use Access Replication, if you are bold, undaunted by code, and willing to read up on this complex subject g. John W. Vinson[MVP] |
#3
|
|||
|
|||
John,
Thanks for the Advice, on both topics, sorry it took me so long to reply. I ended up combining the group id and the auto number. I was just relunctent to do that because i am curious, can i import data without making code to import it. or pretty much to i need to make some code or query instead up derectly importing data? Once again, Thanks! "John Vinson" wrote: On Thu, 13 Jan 2005 15:05:06 -0800, "Nevie and Phil" wrote: Are Primary keys needed in child tables? Primary keys are needed in ALL tables. How important is having a defined primary key in child tables? Essential, if you want to update the table, delete records, sort, .... Here is my dilemma; I have 35 groups running around come desert country. I having them send updates to a central database with something like XML files (I haven’t exactly figured out how yet). The primary table won’t have any conflicts, but I am contimpated the need to have primary keys in the child tables. Could you guys let me know what you think and if it’s worth combining a group ID with an Auto number in the forms (or if there is some way to have the Jet do it maybe by default?) Two suggestions: use a two-field primary key consisting of the groupID and a Long Integer sequential number, probably manually assigned (though an autonumber should work); or use Access Replication, if you are bold, undaunted by code, and willing to read up on this complex subject g. John W. Vinson[MVP] |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
junction tables for 3 many to many relationships | LAF | Database Design | 17 | January 5th, 2005 04:01 PM |
Updating primary key in related tables? | Matt | General Discussion | 1 | September 9th, 2004 05:22 PM |
Using Primary Keys | Jodie | General Discussion | 1 | July 14th, 2004 08:49 PM |
Mutliple Tables lookup? | Westley | Database Design | 4 | June 15th, 2004 01:07 AM |