When you compact/repair a database, Access rebuilds the indexes. If it
discovers duplicate data in a field that has a unique index, it has a
problem. The Microsoft developers decided it would be better to drop the
index rather than the data.
When this occurs, you should have a table with a name ending in
CompactErrors, explaining where the problem lies.
A side effect is that if there was a related table and the referential
integrity depended on the unique index, the relation is also dropped.
This situation does not arise often, though a flaky network increases the
chance of incomplete/interrupted writes.
--
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.
"Skidder1" <sk******@ntlworld.comwrote in message
news:11*********************@g4g2000hsf.googlegrou ps.com...
>
Has anyone ever had an issue in MS Access 2003 where the primary key
of a table has just disappeared overnight? The database is on a
server file share, is in native MS Access and is split into code/data
files but is not unusual in any way from any other I have seen. The
only differenbce (for me) is this is the first 2003 dB I have come
across, normally I develop with 97 or 2K. I have scanned various
group histories to see if anyone else has expoerienced this issue but
have not come up with anything yet.
Thanks
Skidder1