Second, I assume the database is multiuser and you are asking about compaction of the "back-end"...if so, you will need everyone to be out of the database when you compact (otherwise you risk corruption). This makes compact-on-close a very bad idea, you have no real control over when someone is closing the database.
Second, compact-on-close can, on large databases or slow manchines, cause a long delay when closing the database. This may frustrate the user.
The only place you might select "compact-on-close" is the "front-end" database, where the forms, reports, queries, etc. are located. Even then, your front-end shouldn't bloat with usage, and shouldn't need compacting.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.