I am still a little unsure of the exact nature of your problem, but
perhaps these comments will help.
EXPLANATION??? Using an autonumber as a keyfield can create problems,
because when you start moving record between tables autonumber re-assign
values in the primary key field. For example, let's say you want to
copy a record from table A to table B. Both tables have primary key
fields named ID# of the type autonumber. When you copy the record with
ID# 5 from Table A to Table B, its ID# will probably change. The
records new ID# will be generated by Table B's autonumber field, and be
equal to Table B's greatest ID# plus 1. For this reason **Your primary
key field values are not stable when you transfer records.**
Perhaps in your case, when you transfer records to a table with a
foreign key, it can't find the foreign key value it is looking for and,
due to referential integrity, does not allow the records to be copied.
SOLUTION???? I would suggest not using autonumber for a primary key
field. Instead, use long integer, and set the default value to
=GenUniqueID(). This way as records are added, they will automatically
be assigned a unique value, and that value will remain stable.
--
Tenbroeck G. Smith MA, Project Coordinator
Rollins School of Public Health - Emory University
1462 Clifton Road, Room 513
Atlanta, GA 30322
Work: (404) 727-8450. Fax: (404) 727-7261