Skip_Laughlin
asked on
Access 2000 Database Crashes-Urgent help needed!
I am visiting a client's site. He is running a VB app that I wrote and it uses Access 2000 databases. He has been working on this particular database for several weeks and it has a substantial quantity of data that will be tough to replace.
If I import the MDB to my laptop and try to open it with a current copy of the EXE, it crashes immediately. I've tried following it with the debugger and it crashes when VB invokes the SET DB statement.
If I put a current copy of the EXE on his PC and try it, it crashes.
I tried importing the tables to a blank database, but the instant I tell it which external MDB to get the tables from, Access crashes.
HELP! Major event starts tomorrow!
If I import the MDB to my laptop and try to open it with a current copy of the EXE, it crashes immediately. I've tried following it with the debugger and it crashes when VB invokes the SET DB statement.
If I put a current copy of the EXE on his PC and try it, it crashes.
I tried importing the tables to a blank database, but the instant I tell it which external MDB to get the tables from, Access crashes.
HELP! Major event starts tomorrow!
ASKER
Sorry, I posted this in the wrong area.
But I saw your suggestion on another question. I can't open the database to compact and repair, or import tables, or anything else. It crashes as soon as access addresses it!
But I saw your suggestion on another question. I can't open the database to compact and repair, or import tables, or anything else. It crashes as soon as access addresses it!
ok ... sorry ... I see its a VB app. Well .. decompile won't do anything if just tables in the MDB ... but the Compact & Repair may help.
mx
mx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I finally sent it to a professional recovery service. While waiting on the reply from the first service, I also sent it to one in the UK. The first service soon replied that the data was unrecoverable. Much anxiety at this point. 20 minutes later, the UK service sent me a report showing which tables he could recovere. It was all of them!! $60 later, I was a happy camper.
Thanks for the suggestion. I hadn't thought of using a service.
Thanks for the suggestion. I hadn't thought of using a service.
What was the service name ?
mx
mx
ASKER
Thank you Skip ...
mx
mx
But first, if you have not already:
Check for any **Missing References via the VBA Editor>>Tools>>References ....
Then, follow this procedure:
0) **Backup your MDB**
1) Compact and Repair the MDB, as follows:
Hold down the Shift key and open the MDB, then from the menu >>Tools>>Database Utilities>>Compact and Repair ...
2) Execute the Decompile (See example syntax below) >> after which, your database will reopen.
3) Close the mdb
4) Open the mdb and do a Compact and Repair (#1 above).
5) Open the mdb:
a) Right click over a 'blank' area of the database window (container) and select Visual Basic Editor. A new window will open with the title 'Microsoft Visual Basic' ... followed by then name of your MDB.
b) From the VBA Editor Menu at the top of the window:
>>Debug>>Compile
Note ... after the word Compile ...you will see the name of your 'Project' - just an fyi.
6) Close the mdb
7) Compact and Repair one more time.
*** Executing the DeCompile:
Here is an example of the command line syntax (adjust your path and file name accordingly) for executing the
decompile:
Run this from Start>>Run, enter the following command line ...
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
"C:\Access2003Clients\AzDo
For more detail on the Decompile subject ... visit the Master on the subject (and other great stuff) Michael Kaplan:
http://www.trigeminal.com/usenet/usenet004.asp?1033
mx