VBA Project in the Database is Corrupt

  • Thread starter Thread starter Scott Duncan
  • Start date Start date
S

Scott Duncan

Hello,

We are getting a VBA Project in the Database is Corrupt error.
Compact & Repair will not run.
Tried on a number of different machines, same error...
Can not Delete any forms, export to an external mdb or anything.
We can not even open up the VBA editor.

Any help would be greatly appreciated.

SD
 
Have you tried to open it with the /Decompile Switch? (remember to hold down
the SHIFT key 'till a MsgBox pops up)
ie shortcut with target:

<path to access>\msaccess.exe <path to db> /DECOMPILE

Pieter
 
Scott Duncan said:
Hello,

We are getting a VBA Project in the Database is Corrupt error.
Compact & Repair will not run.
Tried on a number of different machines, same error...
Can not Delete any forms, export to an external mdb or anything.
We can not even open up the VBA editor.

Any help would be greatly appreciated.

SD
Click to expand...

This, in my experience, is unrecoverable, except by resorting to a backup.
 
Scott Duncan said:
Hello,

We are getting a VBA Project in the Database is Corrupt error.
Compact & Repair will not run.
Tried on a number of different machines, same error...
Can not Delete any forms, export to an external mdb or anything.
We can not even open up the VBA editor.
Click to expand...

When you say you can't export to an external mdb, does that mean you
tried creating a new database and *importing* from the corrupted one?
 
Scott Duncan said:
Hello,

We are getting a VBA Project in the Database is Corrupt error.
Compact & Repair will not run.
Tried on a number of different machines, same error...
Can not Delete any forms, export to an external mdb or anything.
We can not even open up the VBA editor.
Click to expand...

What version and service-level of Access? Have you applied all service
packs?

Did this occur in a database that was converted from a previous Access
version?
 
In my experience this is not good. Hopefully you have a backup, if you don't
you've got a big problem. I'll bet a good deal of the people developing in
Access have encountered this so don't feel too bad.

On a daily basis, first thing in the morning, I do the following with my
projects. I back up the previous nights work, copy it to an archive folder
after renaming it with the days date and alpha characer. (db20041019A.mdb) I
then open Access and click cancel on the prompt to open a database and then
compact and repair the renamed file back to the original file name. I've had
bad luck when I've repaired over the top of an existing mdb. During the day
as I work on the db I keep track of the size of the database, and when it
doubles in size I do it all over again. I store my data externally so adjust
this formula if you store data in the mdb. You are going to have to
experiment with the formula I have no idea on a good guidline with internally
stored data. I've noticed my databases start acting strangely when they get
to about 3 times or greater than they were when I started working on them.

The one time I've encountered this problem since I started this process was
caused by deleting a form that other forms had dependencies. Since I had a
backup that was an easy recovery.

BTW - I'm working with Windows 2000 and Access 2000, I'm comfortable saying
this applies to 97 since I've had issues like this with it. On newer versions
of Access I have no idea, haven't worked on them.

~Mark
 
Dirk,

We are using Access 2003 with Office SP1.
No, this error did not occur while converting from a previous version.
I was editing a form... When it came time to save the form, the message box
had the form name
listed twice i.e. Order Form and Order Form1. I clicked to save all.

I have tried both, exporting from the corrupted database to a new one and
vice versa.

Thank you for your interest.

SD
 
Back
Top