MsAccess 2003 code rollback after compacting

[Guest]

Has anyone had their functions or subroutines rolled back to a prior state
after compacting an Access database even though they saved the changes prior
to compacting the database? I have had this occur on multiple occasions and
need to find a reliable way to trap when this happens. This event occurs
even when several days or weeks elapse before compacting the database.

I have made changes and compiled an MDE for the users and the enhancements
are intact and work as they were intended. A few days or weeks later another
enhancement will be requested to a different module and after the coding is
done and the database compacted the prior enhancement in the other module no
longer exists and we are back to the old code.

I have the MDB that I code from on my local hard drive and the backup copies
are stored out on the network and the MDB is saved locally and then after
exiting Access is copied over to the backup directory, so I know it is not
user error opening the wrong MDB and overwritting the current version with
old code.

 

[Metra]

It has happened to me at one client's repeatedly with Access 2000, but not
2002. Has happened with another consultant I know with a 2000 file format.

 

[Guest]

Was there any resolution or programatical trap to reveal what had been rolled
back? There is no warning when this happens and I hate to be caught by
surprise.