Has anyone gotten the "The Visual Basic for Application project in the
database is corrupt" message. This message shows up several times, and is
finally cleared after sufficient OKs.
This started after I made a change to the Design Master. As in the past,
I
make a change to the DM.
The DM is direct synced to the replica farm at 12:15 am. This is when the
system tends to be idle. It's a scheduled sync. It follows a 12am
scheduled sync which is done every hour between the replicas of the
replica
farm. These syncs appear to have finished without errors.
The new table has been replicated to all replica databases; however they
all
have the above error message. The application still works, and no data
appears to have been lost.
One of the message points to a bad "Module1". Of course Access 2002 won't
let me open or delete it.
Another message suggested direct syncing the DM to the replica. Did that
(from Replman) it worked; but did not resolve the problem.
When I get the DM open in Acess (after all the messages), it will not let
me
do a compact / repair. Nor will it allow a compact/repair done from from
the Access command line.
Access 2002 (XP) is current to SP3.
Any thoughts?
I'm considering making a new DM and hoping that Access will not bring over
the bad module (which is left over from development and not used in
production). Another option would be to delete the module via a program.
TIA
Don
