mde file swells up (Access 2003)

[DavPet]

My front end is an mde file. About 12 people use it. After a few days, the
file size doubles; in a week it is 3 times bigger than it was when I
compiled it. All but one of the data tables are in the backend. The
frontend only has the switchboard table and the usage table in it.
The usage table is small and stores the userd ID and time.

Decompile and compact gets the size back down again.

Why does it grow?

 

[tina]

i'm guessing that your usage table is recording who is currently using the
database, and what time each person opened it? so each time a user opens the
frontend, a record is added to this table, and the record is then deleted
when the user closes the frontend? each time a record is added, the db size
increases. when the record is deleted, that "empty" space is not released
until you compact the db. that probably accounts for at least part of the
frontend bloat.

hth

 

[Guest]

I think you meant to say Compact and repair gets the size back down again,
since you cannot decompile a .mde file.

Have a look at the various KB articles at this link:

http://tinyurl.com/2dmpw

Finally, you should not have users sharing a common front-end file. Each
user should have their own copy installed on their local hard drive. If you
want, you can set the Compact on Close option to help keep the file from
growing too much.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

My front end is an mde file. About 12 people use it. After a few days, the
file size doubles; in a week it is 3 times bigger than it was when I
compiled it. All but one of the data tables are in the backend. The
frontend only has the switchboard table and the usage table in it.
The usage table is small and stores the userd ID and time.

Decompile and compact gets the size back down again.

Why does it grow?