Scribd
Upload
26 views

MDBDeco Read Me

The document provides information about MDB Decompiler, a tool used to decompile Microsoft Access mdb files. It decompiles files to remove extraneous data from updates and deletes, reducing file size. The decompiler resolves glitches in code and cuts file size beyond what compacting achieves. It has a simple GUI with buttons to select mdb files and start decompiling. Requirements include Access 97 or 2000, disk space, and that files contain VBA code/objects to be affected. Decompiling only tables does nothing. It notes the decompiler uses an undocumented Access feature so backups are made and replaced files are numbered for safety.

Uploaded by

sk2sysj
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
26 views

MDBDeco Read Me

The document provides information about MDB Decompiler, a tool used to decompile Microsoft Access mdb files. It decompiles files to remove extraneous data from updates and deletes, reducing file size. The decompiler resolves glitches in code and cuts file size beyond what compacting achieves. It has a simple GUI with buttons to select mdb files and start decompiling. Requirements include Access 97 or 2000, disk space, and that files contain VBA code/objects to be affected. Decompiling only tables does nothing. It notes the decompiler uses an undocumented Access feature so backups are made and replaced files are numbered for safety.

Uploaded by

sk2sysj
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 1

PB-Sys MDB Decompiler F.A.Q.

Description: MDB Decompiler is a simple tool used to decompile a Microsoft Access mdb file (A97 or A2000). Typically, an Access database grows over time due to updates, deletes, and additions. With updates and deletes, data is discarded but not removed. Typically, a compact database operation will remove cleanup and remove this extraneous data. However, does the same thing occur withforms, reports, and modules? The answer is yes, and the cleanup fix (force binary decompile back to just active objects) is to run the undocumented Access /Decompile switch. This tool is needed for the following occasions: Resolve GPFs in code that are seemingly inexplicable and continue to recur despite routine repair and compacts. Cut file size beyond what repair and compact does to data tables (for cleanup and size reduction). You can look at the screen shot below for an idea of how the GUI works. It is a really simple, single dialog application. That dialog contains one text box into which you pick an .mdb files to decompile. There are browse buttons to assist with file selection (dont have to type entire path in). 1. Use the browse file button ( ) to select a target mdb file.

Need:

Usage:

2. Press the Finish button to backup, decompile, and compact the mdb file. Requirets: The following list of requirements is necessary for MDB Merge to properly function: 1. Microsoft Access 97 (or Access 2000) 2. 1MB of hard drive space 3. Pentium II or better 4. Only mdb files containing VBA code and objects including modules, reports, or forms should be decompiled. Decompiling .mdb files that only contain tables will do nothing. Here are some technical notes regarding the application: /DECOMPILE is an undocumented Microsoft Access feature, so they suggest that you use it with care. Because the /decompile switch is undocumented, it has some inherent risk. To mitigate that risk, backups made of the original database, and the .mdb is replaced with .001, .002, .003 and so on up to .999. It is up to you to clean these files out as needed. Cue cards ( ) can be clicked to popup a message box describing a given GUI feature.

Notes:

You might also like