Front End increases in size after decompiling.

[ser01]

So today I decided to decompile/recompile my front end. That is manly because lately I have made a lot of changes/addition to my VBA and wanted to make sure I clean it all up. This is the first time I have done this and something unexpected has happened. Before I decompiled I compacted my FE. The file size after compacting was 2.8 Mb. After I decompiled/recompiled and compacted again the size is 3.2 Mb. I expected the file size to shrink, but instead it grew. I have done it several times and every time the same thing happens. Can anyone shed any light as to what may be causing this?

[RuralGuy]

After a /decompile then do a Compact and Repair *before* compiling again.

[ser01]

After a /decompile then do a Compact and Repair *before* compiling again.

Just did, same exact result. Not that this is a problem, just very peculiar and was wandering what it may mean.

[RuralGuy]

Is the size of the db smaller *after* the /decompile but *before* the recompile? Interesting results.

[ser01]

Is the size of the db smaller *after* the /decompile but *before* the recompile? Interesting results.

Here it is step by step:
After I compact and repair the size is:
2,818,048 bytes
Imediately after I open the file with the /decompile the size is:
2,883,584 bytes
After compacting and repairing again the size is:
2,740,224 bytes
Went in the database tools and opened visual basic, then compiled and saved. Size is:
4,014,080 bytes
Compacted, repaired and closed. Size is:
3,252,224 bytes

By the way opening with the /decompile command as well as repairing is done while holding down the shift key to prevent the start up code that i have from running.

[RuralGuy]

The file should be smaller after a /decompile and Compact and Repair. The inconsistancy you are seeing with a compiled db are not uncommon and probably an artifact of the algorithm used to C&R. Access reorganizes during a C&R and reindexes as well.