[AccessD] Good Code Bad Code Question

Charlotte, renaming a database is supposed to force a decompile. When you
open, run Compile from the Debug window. It might be an easier shortcut for
some -- especially for those with really huge systems and path names that
include all kinds of weird convention names and stuff. I know I've always
used it -- rather than the command line switch. 

I'm having trouble with 2003 and 2002 -- just nothing's working all the
sudden. I ran an Office Repair, but they're both still wacky. I'm going to
have to reinstall -- can't see any way out of it. 

But, on a lark this morning, I tried a decompile using the rename trick on
one of the mdb's that's showing distress and I noticed that once it
recompiled, the Compile option on the Debug menu displayed the OLD name, not
the new one -- weird huh? So, I'm wondering if the rename decompile trick
really works as good as it's supposed to? Or, this could just be more of my
exe's wackiness. Anybody but me ever experienced this? 

Susan H. 

Joe,

To decompile, use a command line argument in opening the database.  That
means you have to fully reference the path of the Access executable and the
full path of the target database or the /decompile switch will be ignored.
After you open the Access database that way, close the Access session, then
reopen the database normally without the decompile switch, go to the VBE and
use Debug-->Compile... To recompile the app.  This clears out some crud that
may otherwise cause you grief.