Access 2007 - Intederminate relationship

Imports tend to be quite specific. There are so many problems that can
occur, e.g. inconsistent columns (data above/below/in the middle of the
valid columns that are just comments), inconsistent types (e.g. "N/A" in a
date column), new columns inserted since last import (so the columns are not
in the right order, or the names in the first row are different),
inconsistent data (e.g. "Acme Corp" is company 123 in the first row, but it
is company 456 in a later row), and so on.

Additionally the good data structure you are trying to import into varies
(e.g. a column can't be null, or has a validation rule, or is uniquely
indexed, or there is a validation rule, or has to match a foreign key value,
or ...)

Therefore the import routine needs to be written to test the data. One
approach is to import it (as is) into a temporary table, where you can run a
series of tests for all the things that could go wrong, and provide a form
where the user can fix the bad data. Once all critical problems are fixed,
you execute the series of append query statements that will write the data
into the real tables in your database.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"kgoo" wrote in message
...
Hi Allen,
Do you know where I can find information on writing a good import routine?
I have a huge "company" spreadsheet of about 16,000 records and an agent
spreadsheet of about "8,000" records.
Let's say all my data uploaded without any problems... do you think the
structure of the tables should work based on my information provided?