The assumption I have is that the Master table and the Archive table are
duplicate in structures. The Master table, I assume, has a Primary Key field
that is of type 'autonumber'. The equivalent field in the Archive table does
not necessarily have to be 'autonumber' but it should be of type 'Long'.
Based on this, there should be no concern/issue with the moving of records
from the Master to the Archive, that is, the records from the Master are
copied and deleted.
It is my belief that there is 1 of 2 things happening in the application:
1. Some process is compacting and repairing the database some time after
transfer from the
Master table to the Archive table occurs; or
2. Some process is occuring to reset the autonumber in the Master table.
If #2 is occurring, then I would suggest for this to not occur... unless
there was some absolute necessity for this to occur.
If #1 is occurring, then find out WHEN it occurs.
See what information you can provide back and I will see what I can best to
to help you continue from here.
Rob
--
Rob
FMS Professional Solutions Group
http://www.fmsinc.com/consulting
Software Tools for .NET, SQL Server, Visual Basic & Access
http://www.fmsinc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
ACCESS said:
The numbers were repeating in the master table or one in master table and
one in archive table. (in this case, it would not append to the archive
because the number already exist in the archive table).
What would you recommend to fix this? should i have more than one primary
keys or no primary keys at all??