FE MDB file grows excessively with normal, non-development use

[Guest]

I have a front-end (FE) mdb file which contains 57 forms and subforms, 32
queries, 55 reports and subreports, and 4 modules with linked tables to 64
SQL Server database tables and views. After a compact and repair of the
front-end, the database is approximately 6MB. Within about a week, with
between 5 and 10 simultaneous users at any given time, the front-end grows to
an excess of 80MB (but no data is being saved in the front-end)! There are
no dynamically added tables, query-defs, forms, or reports. The application
opens existing forms, reports and queries, and uses recordsets for doing
batch record processing functions.

None of the users are 'designing' the forms, queries, or reports, so I don't
believe any objects are being created or destroyed through the normal usage
of this application. What would be an approach to begin to look at what is
causing the severe growth to the front-end mdb file? A security limitation
prevents us from compacting and repairing this database automatically and,
besides, I don't really just want a work-around... I want to learn what it is
that is causing this unprecedented growth in an MDB that doesn't have objects
being created or destroyed!

Thanks in advance!

- Ed

 

[Albert D.Kallal]

I assume that each user/workstation gets a copy of the FE..right? (you can't
have more then one user into a FE...so each user gets a copy).

Further, each user should in fact get a mde,not a mdb (this can also help
the bloat problem, as it forces/keeps the code compiled).

Further, if using a2000 or later, then set the database to compact on
close.This will solve the bloat problem for sure!

Do all 3 of the above, and your problem will be solved...