Compiled VBA

When you compile an MS Access application, where is the compiled stuff stored? Is there a hidden system table?

Your explanation of "Bad DLL Calling Convention" says:

...over time, the part of your Microsoft Access database that stores VBA module code can become bloated, and in some cases, trigger strange errors such as Bad DLL calling convention.

As you compile and run code, VBA leaves behind old versions of the code that are no longer valid, but it is not always removed from the database.

Fortunately, Microsoft Access has a solution with the /decompile command line option.

When MS Access is started with this and you open a database, it discards all the old compilations and leaves just your VBA source code. You'll need to compile again to get the compiled state. After compacting, your database may be significantly smaller.

Compiled VBA

...over time, the part of your Microsoft Access database that stores VBA module code can become bloated, and in some cases, trigger strange errors such as Bad DLL calling convention.

As you compile and run code, VBA leaves behind old versions of the code that are no longer valid, but it is not always removed from the database.

Fortunately, Microsoft Access has a solution with the /decompile command line option.

When MS Access is started with this and you open a database, it discards all the old compilations and leaves just your VBA source code. You'll need to compile again to get the compiled state. After compacting, your database may be significantly smaller.

Comments

Didn't find what you were looking for?