"I assume that means to open up a blank database and import everything from the old? "
That is always a good idea - if you are planning on converting.
Here is the Decompile drill - which you can do after importing into a new mdb:
But first, if you have not already:
Open the VBA Editor and from the menu ...Tools>>References ....
If you see any listed as **Missing:
, including the asterisks and the word Missing, the
you need to fix that first.
Then, follow this procedure:
****
0) **Backup your MDB BEFORE running this procedure**
****
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 ...
Close the mdb after the Compact & 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) Close the mdb.
6) 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.
7) Close the mdb
8) Compact and Repair one more time.
*** Executing the DeCompile **EXAMPLE**:
Here is an **example** of the command line syntax (be SURE to adjust your path and file name accordingly) before executing the decompile:
Run this from Start>>Run, enter the following command line - **all on one line** - it may appear like two lines here in the post:
Also, the double quotes are required.
"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile "C:\Access2003Clients\YourMdbNameHERE.mdb"
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
