Compacting an access database

[HOW1]

Hi,

I have designed a database which has been split into a front end and back
end database. I have set-up both the front end and back end to compact on
closure. However the open and closure of the back end is driven by the front
end of the database therefore I am unsure if the compact on closure is
actually taking place. Can someone please advise.

Thanks in advance.

Regards

 

[Douglas J. Steele]

No, the back-end isn't being compacted through the Compact On Close option.
In actual fact, it's not a good idea to use it on the front-end either.

 

[John W. Vinson]

Hi,

I have designed a database which has been split into a front end and back
end database. I have set-up both the front end and back end to compact on
closure. However the open and closure of the back end is driven by the front
end of the database therefore I am unsure if the compact on closure is
actually taking place. Can someone please advise.

Thanks in advance.

Regards

It's not necessary to ever compact the frontend; if it doesn't have tables it
shouldn't bloat much, and if it does you can just junk it and replace it with
a new copy.

And a shared backend should not be compacted-on-close either, since you can
run into conflicts with other users.

Instead, compact the backend manually or programmatically, only when necessary
(e.g. when it's doubled in size).