Hi Jan ! Did you just reply to your own thread ? ;) Before you go any further, you may want to browse around on line and read up on databse design, specifically normalization, keys and the like. (If you haven't already) I normally don't start creating tables, queries, or write code until I have a good idea in my head what my tables will be, what data they will hold, what the promary ad foreign keys will be, etc.
--- On Sun, 1/18/09, Jan <[email protected]> wrote: From: Jan <[email protected]> Subject: [ms_access] Re: Database design question-problem solved To: [email protected] Date: Sunday, January 18, 2009, 6:53 PM I played with the upload and it is pretty obvious I need to keep all the data in one table even though some of it is from an Excel upload and some is input. Thanks Jan --- In ms_acc...@yahoogrou ps.com, "Jan" <phssthpok3@ ...> wrote: > > am designing a database for our PMO staffing function. I am thinking > about the master Position/Requisitio ns 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 > [Non-text portions of this message have been removed]
