Question Database Options

[DreamGenius]

As a rule, when starting a new database, I set certain things up in advance, such as Tools > Options > General > Compact On Close in MS Access and Tools > Options > Editor > Require Variable Declaration in VBA IDE.

I've now started exploring MDEs to keep users from playing about with my developed application (and breaking it) and they appear to compact on close, as required, but create an MDB file, which I obviously don't want.

I suspect it's as simple as disabling Compact On Close and recompiling the MDE but:

1. Is it necessary or advisable to Compact On Close when using an MDE
2. Can I somehow force it, without using tons of code, to revert to MDE after Compacting

I'm after (suggested) best practice rather than simply what works; that I can find out for myself! Thanks as always ...

 

[DCrake]

The compact on close feature normally applies to mdb's that contain the data. MDE's usually have everything bar the tables (which are linked) and as such should have no reason to bloat. However someone will deny this. The only way it can effectably bloat is if you are doing make tables and appends , deletes to tables inside the mde. I have never tried to compact an MDE and as such never noticed it making it an mdb.

David

 

[DreamGenius]

Just to clarify, my MDE does not contain any tables - they are linked via UNC path per recent advice on this forum. On that basis, is CDrake's experience universal and should I just remove the Compact option before compiling the MDE?