It's always worth finding out what the relationships are between your data. For example is there a relationship between position and requisition....does one position have more than one requisition and is each requisition only associated with one position. Only then can you determine your primary and foreign keys.
For FREE Access ebook and videos click here http://access-databases.com/ebook --- In [email protected], "Jan" <phssthp...@...> wrote: > > am designing a database for our PMO staffing function. I am thinking > about the master Position/Requisitions table. They get a weekly Excel > extract from another database with changes and new positions. The > primary key will be the client requisition number. > > The PMO staff will add to this 2 more identification numbers when the > information is added to our external recruitment system and our system > for sub-contractors who provide staff. (I don't like it either, but > there it is) > > Should I put all 3 reference numbers in the primary table and deal > with any upload problems or create a second table with the client > requisition number as primary key and then add the other two reference > numbers there? I would rather have only one table but I am worried > about the weekly upload. > > Thanks > Jan >
