Front-End Ballooning

[jgelpi16]

I have a DB that I recently converted to .accdb format in an effor to eliminate the "Updating Tables" issue. I have it split into a front end and a back end. At the beginning of the day the front end starts out at around 20KB. By the end of the day it has been at 250KB! Users are experiencing extreme sluggishness. I have the database set to compact and repair on close but this database is accessible state-wide so it usually isn't truly closed until the end of the business day. Any suggestions as to how I can eliminate the ballooning? The entire DB is located on a central server (front end and back end) and the field users access it through Citrix. Deploying front-end to user's machine is undesireable because DB still runs very slowly.

[TheShabz]

If all the users are still using the same front end, you've defeated the purpose of splitting your DB. a split DB should ahve one front-end for each user located on their local machines with the backend on a server. If you aren't doing that, you might as well create an .mdb with a user login form.

[RuralGuy]

With Citrix each user should be using a *different* copy of the FrontEnd. They would be on the host computer and not on each local machine.

[TheShabz]

Yes. Thanks for the clarification RG.

[RuralGuy]

No problem. We're all in this together.