Compress On Exit

[Derrick T. Davidson]

What are the pro's and con's and setting the database to compress on Exit?

[ItsMe]

Users may need access when you go into exclusive mode during Compact.

[burrina]

It has long been suspected that Compacting leads to corruption. What is the Real Need?

[June7]

We also know that db can grow from design edits. Compact & Repair 'cleans up' the db. Running C&R on development master frontend should be done after design edits. C&R on backend should be rarely needed. Really no reason to do C&R on user copies of frontend. Whether split or all in one, make sure no one needs the file when running C&R.

[NTC]

The major con is that On Exit can be triggered by or occur during power failures/flickers - and while there is seemingly low probability of that - why take a chance. It is a bad idea in general, as the Compact & Repair should be only triggered in a controlled situation with a human thinking and knowing why they are doing it - not put onto automatic drive. When it is needed, and that is rare - it can be extremely helpful. Certainly today there are no real issues of file size relative to disk size like there might have been in the 80s. So it should only be invoked when corruption is suspected.

[Derrick T. Davidson]

Thanks to all guess will not invoke this option, many thanks