MsysCompactError, Paste Error, Relationships missing

Is it possible for a Repair and Compact to actually remove all the relationships in a database, as well as the primary key in the main table due to a MsysCompactError, and then a Paste Error?  I am trying to determine what happened, as I think someone might have been fooling around with the DB, but I want to make sure what this is before I point any fingers.  

We do almost daily repair and compacts, and I take random backups (in addition to the network backups every night).  I went to make a change in the DB and noticed that all the relationships were missing, and the primary key in the main table had been removed.  Around that time a rather inept SQL programmer had been asked by management to look into importing the back end into SQL, so I intially assumed that he had messed up the table and then reimported it without knowing what he was doing.  Now though, I have discovered the MsysCompactError table and Paste Error table in one of my backups, and this is the first one where the relationships disappeared.  Database is working fine, and those two tables seemed to magically disappear on their own - would the next successful repair and compact get rid of them?  

Sooooo...is it possible for all this to occur just because of an error during repair and compact??????  And is it possible for the tables to disappear on their own?  Or has someone been monkeying with my DB :(
LVL 1
bcadAsked:
Who is Participating?
 
Jim P.Connect With a Mentor Commented:
If compacting over the network this is very possible.  I suggest that you copy the database locally to your workstation or do it from a remote desktop on the server.  And use the jetcomp utility instead of the Access compact.

http://support.microsoft.com/kb/295334/en-us
0
 
bcadAuthor Commented:
I have never before seen a Paste Error table delete itself though, so this is what made me suspect that it had some help.  Is it possible for Access to delete the Paste Error and MsysCompactError tables all by itself??

0
 
Jim P.Commented:
The MsysCompactError is created at compaction by access.
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
bcadAuthor Commented:
Yes, I understand that, but is that a table that would be deleted automatically the next time you successfully repaired and compacted?
0
 
Jim P.Commented:
Exactly.  It looks like you have a bad compact/repair.  Yo probably need to go back and restart from the last known good database.
0
 
bcadAuthor Commented:
And this bad compact/repair could delete primary keys and relationships in the DB???  I have never seen this happen before...
0
 
Jim P.Commented:
If you have a DB that is looking for the MsysCompactError that means it wasn't a good, complete compact and repair.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.