A properly designed Access application should be split into a front-end
(containing the queries, forms, reports, macros and modules), linked to a
back-end (containing the tables and relationships). Realistically, it's only
the back-end that needs to be compacted regularly. Since chosing the
"Compact On Close" option only impacts the front-end, it's of limited value.
I question your comment, though, that "Compacting an Access application can
corrupt an Access MDB." While that's true, doing anything with an Access MDB
is, theoretically, capable of corrupting it. Compacting is a fundamental
part of proper maintenance of Jet databases, and should not be avoided.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is it risky to automatically compact an Access MDB when a user closes
> an application.
> That is automatically compacting by checking Compact on Close on the
> Option form in the Tools menu.
> Compacting an Access application can corrupt an Access MDB.
>