Home  |  About  |   Search   

What's New
Table Of Contents
Credits
Netiquette
10 Commandments 
Bugs
Tables
Queries
Forms
Reports
Modules
APIs
Strings
Date/Time
General
Downloads
Resources
Search
Feedback
mvps.org

RunCommand Constants

Terms of Use


 

Bugs: Solving Access IPFs with /Decompile

Author(s)
Michael Kaplan
 Often times, your application may started causing General Protection Faults in various internal objects or dependent dlls.  These errors do not seem to get fixed by compact/repair.  Access 97 has an undocumented /decompile command line option that very frequently fixes this type of problem.
Usage:

    msaccess.exe /decompile "c:\something\OrTheOther.mdb"

Access 2000: There is no UI associated with the command line option. Therefore, you will get no message boxes or any other visual indication that the project has been decompiled (except checking the Compile and Save all Modules menu option).

Caution:

    Decompile is a powerful option.  Use it with caution, in cases where the db is corrupt, and not with a constant frequency.  More details can be found at this link, thanks to Michael Kaplan.

The real deal on /decompile switch

    To the best of what I know, (thanks to Michael Kaplan) /decompile tricks Access into thinking that the binary format of the database has to be changed. This automatically decompiles the entire database. 

        As is evident from the cases when it's solved the problem, this option works more often in resolving IPFs than any patches.   So if everything else fails, give this a try!!

Disclaimer: 

        Being an undocumented option,  there is no guarantee that it will be present in the future versions of the product. 


1998-2009, Dev Ashish & Arvin Meyer, All rights reserved. Optimized for Microsoft Internet Explorer