Compact and repair

[Guest]

Hi,
Can you please explain, compacting and repairing in a split database is made
to the Front End or to the Back End file?

Thanks
GL

 

[Guest]

Hi,
normally the frontend does not need to be compacted. It doesn't change in
design anymore and in many cases is compiled. The only reasons to compact the
frontend would be if you constantly create/delete temp tables of some sort.
The compact and repair is important on the backend, but be aware that this
should be either done on the machine the backend is stored, or copy the
backend down to your local machine, then compact and repair and then move it
back to the server. You should NOT compact and repair over the network.
HTH
Good luck

 

[Guest]

If you are compacting the front end, it will compact the front end only, if
you compact the back end, it will compact the back end only.

 

[Guest]

Is it usefull and safe to use the Compat On Close Option?

 

[Douglas J. Steele]

Not particularly. The Compact On Close option will only affect the
front-end, and as Oliver pointed out, compacting the front-end isn't all
that critical in an application that's built properly.

 

[Guest]

I've read somewhere else in this forum that that Compact on Close also
compacts the BE as soon the last user closes the application, or that it is
not a good practice to compact through the network.
What is your opinion about those?

 

[Douglas J. Steele]

No, Compact On Close has no impact on the back-end.

Compacting through the network can increase the possibility of corruption,
especially if your network (or the NIC on that machine) is a little flaky.
Access has been described as "a canary in a coal mine": if something's wrong
with the network, Access is likely going to find out for you! You could copy
the MDB locally before you compact it, although that's not always practical.