Dan
Split your multi-user database so each user has a local front end with everything but the tables. Put the back end with the tables in a shared folder. See my article on deploying and updating front ends at http://thatlldoit.com/howtosarticles.aspx#fe_updater
Set the front end to compact on close if you want, but uncheck that option on the back end.
Then just do routine maintenance to compact the back end, but be sure to move it to your local drive before compacting. Then move it back when you are finished.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile/Bill.Mosca
--- In MS_Access_Professionals@yahoogroups.com, Dan Fielding <amessyguy@...> wrote:
>
> I will sometimes use the Compact on Close option on a particular file. Typically these are files that only I will use (or maybe just a few others). I like how well this reduces the file size, but...I am a little worried about using it on a file that will accessed by many users and one that can be fairly large. Should I be concerned about turning on this automatic feature? Is there a chance that while compacting something could go wrong? Given that there may be a number of users accessing the file what happens if someone leaves it open on their computer? Will the database never be compacted until all users quit the program?
>
> Basically, is this safe and okay to use, or should I probably avoid it?
>
> Thanks for any thoughts on this.
>
> Dan
>
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar