Stranger wrote in
:

Looking at my relationships again, I have the Employee table setup as
the parent table. All of the others are child tables. I think that
is what I have done. I'm still learning this database stuff.

I have one to many relationships from the other tables back to the
employee table. Since an employee can be assigned more than one
computer.



Stranger wrote in
:

The current inventory table contains all of the fields along with an
employee field. The autonumber field is the primary key. Nothing
else unique with the current table.

I did run the seperate append queries and loaded the computer info
into the computer table, printers into the printer table and employee
names into the employee table. The employee table would be the one
to many table.

So, I would now need to reassociate the employees with the new
tables.

I tried to use an append query in access to append the data into all
tables at one time but it won't let me do that.
I know I am rambling now. Should I have the other tables related to the
computer table and not to the employee table?

It would be something like:

Employee
Computer
printer
handheld

Instead of what I have now which is:

employee
Computer
Printer
Handheld

Unless it doesn't really matter.




I've attached wordpad document with two print screens. Hopefully
this will help explain better.






"Ken Snell" wrote in
:

How is an employee related to a hardware now? What you need to do is
to load the data into the parent tables (the "one" tables), and then
use those tables along with the original table (joining from the
original table to the new tables on a field that uniquely identifies
the data in the parent tables) in order to append data into the
child tables (the "many" tables). You'll need to give us more
information about your exact setup and data for someone to give you
more specific info.