AXP Bloat

J

johnb

Hi
I have a 20 user db with one FE and several BE's. the
compacted FE is about 17 meg but within 2 working days
its grown to over 100 meg! Any suggestions as to why this
happens?

TAI johnb
 
J

J. Clay

If I recall correctly, the actual "work" is done in the front end, so when
queries are run, etc., if jet uses any temporary storage, it is placed in
the FE and doesn't get reclaimed until Compacted. I am nut overly clear on
the actual machanics, but I think you need to change your structure
slightly.

Each user should have a copy of the master FE on each of their workstations.
This way, there is no chance of conflict in terms of sharing the FE.
Although we use ADPs, the same would apply to MDBs. How we do it is have a
logon script that when anyone logs onto the network, they get the current
master copied onto thier computer to work from. This way, they are getting
a fresh copy at least daily. Also, this creates an easy way to distribute
updates to the application if necessary. The changed app can be copied over
the master, and the next time everyone logs on they will get the changes.

HTH,
Jim
 
L

Larry Linson

johnb said:
Hi
I have a 20 user db with one FE and several BE's. the
compacted FE is about 17 meg but within 2 working days
its grown to over 100 meg! Any suggestions as to why this
happens?
Click to expand...

In some cases, internal workspace used by queries can cause database growth,
but the most likely culprit for excessive and rapid growth would be creating
and deleting temporary tables. If you are doing that, you'll find an example
of creating a temporary database to contain the temporary tables and
deleting the temporary database instead of the temporary tables at MVP Tony
Toews' site, http://www.granite.ab.ca/accsmstr.htm

Larry Linson
Microsoft Access MVP
 
T

Tony Toews

johnb said:
I have a 20 user db with one FE and several BE's. the
compacted FE is about 17 meg but within 2 working days
its grown to over 100 meg! Any suggestions as to why this
happens?
Click to expand...

A few causes of Front End (FE) bloat are:
- using temporary tables in front end for data importing or report
performance
- images, such as corporate logos on many forms and reports
- explicitly close recordsets
- some other more obscure problems

For more info see the Bloating Front End (FE) Microsoft Access
MDB/MDEs Tips page at my website at
http://www.granite.ab.ca/access/bloatfe.htm

Sharing a FE amongst multiple users can also cause this.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Top