B
Bill Nicholson
Hello,
There's a bunch of records I want to take from one table and append to
another identical table in a different mdb. No problem, but when I restore
them to the original table the primary key changes in the records restored
to the original table. Since it's an Autonumber field, the database manager
creates new unique keys at the end of the original table instead of
inserting the records back where they started. This destroys all my
relationships and foreign keys. I'm doing this with T-SQL and APPEND
commands. I append from the original table to the archive table, delete the
recs in the original table, then APPEND the recs back to the original table
from the archive table.
Is there a trick to this or another strategy that I can use?
Thanks,
Bill
Cincinnati, OH USA
There's a bunch of records I want to take from one table and append to
another identical table in a different mdb. No problem, but when I restore
them to the original table the primary key changes in the records restored
to the original table. Since it's an Autonumber field, the database manager
creates new unique keys at the end of the original table instead of
inserting the records back where they started. This destroys all my
relationships and foreign keys. I'm doing this with T-SQL and APPEND
commands. I append from the original table to the archive table, delete the
recs in the original table, then APPEND the recs back to the original table
from the archive table.
Is there a trick to this or another strategy that I can use?
Thanks,
Bill
Cincinnati, OH USA