There are many tricks available to try to fix corruptions.
1. Create a new empty A97 mdb and import all the objects from the corrupt
one.
Recompile the code.
2. Decompile the code.
Make a backup.
Test the undocumented /decompile command line switch.
The single command line looks like this (watch the wrapping!):
"C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE"
"C:\MyDocs\MyFile.mdb" /decompile
This completely removes all compiled code from the project.
Then compact the database and re-compile it.
Then compact again.
See
www.trigeminal.com for reasons why this can be very dangerous.
3. Try the undocumented SaveAsText and LaodAsText feature.
=========================================
If nothing else works:
Peter Miller is the guru for fixing corrupt databases:
http://www.pksolutions.com/services.htm
"Our most popular rescue service is our Data Recovery Service.
Occasionally, databases can become corrupted. Usually the inbuilt Repair
capability will correct the problem, or its possible to create a new
database based upon the corrupted one. If you are unable to recover from a
database corruption problem, and either do not have, or don't think its
feasable to rely upon an older backup of the database, then our service is
just what you need. Data recovery services are provided for a fee ranging
from US$120 to US$1,200 (although the majority of jobs cost less than
US$600). Our success rate for complete data recovery exceeds 96%. If you
would like us to take a look at a damaged Access database for you, then
please complete the form below. "
--
Joe Fallon
Access MVP
Scott said:
I am having trouble converting an Access 97 front-end application to
Access 2000. I am getting several "error while loading Form..." and then
the last message is "The Visual Basic for Applications project in the
database is corrupt". The 97 version has worked fine for a long time, so I
am not sure where to go? Any suggestions would be appreciated.
