compact & repair

[Guest]

If a database is split & a user compacts & repairs the database - are they
compacting & repairing their front-end database or are they compacting &
repairing the back-end or both?

If I create a command button that runs the compact/repair menu item, what
will it be compacting & repairing, front end or back end?

 

[Van T. Dinh]

Only the Front-End.

HTH
Van T. Dinh
MVP (Access)

 

[Guest]

so does that do any good? Is there a way to write code to have them compact
& repair back-end? If so, what is it?

 

[Van T. Dinh]

In my experience, the Front-End gets bloated more often
(since most processing, if not all is done in the Front-
End) than the Back-End so I do compact the Front-End.

I don't trust code in the Front-End to compact the Back-
End since:

1. The Back-End is open when the Front-End is running.
2. There may be other users using the Back-End at the
same time.

(For me, I manually compact the Back-End only once a week
and I haven't had any problem. OTOH, I mainly use SQL
Server Back-Ends nowadays). I am sure there are a few
utilities / codes to do compact the Back-End but I never
bothered with them. You may like to try MichKa's TSI SOON:

<http://www.trigeminal.com/lang/1033/utility.asp?
ItemID=8#8>

HTH
Van T. Dinh
MVP (Access)