Probem: the access database grows too fast...

[Sam]

Hello everybody,
I have a problem with an access database (access 2003) which grows up.
The size after repairing is about 75MB.
The Operating system is win 2003 + sp
This database contains about 250 tables and 2300 queries. There is no code
and no form.

Data are used through VB/VBA code for reading needs or for
reading/writing/creating. The object used to access the base is DAO v3.6,
so, the workspace is on the user workstation.

I have the same database on 2 sites and the code executed doesn't have any
difference.
The problem about the size is present only on one site. On this site, the
size after some hours (5 to 6) goes to 1GB. The traffic, concerning the
connection, is about 4 to 5 times more important than on the other site.

On the other site, the database grows but with a more "normal" way (it goes
from 75MB to 150MB on a day)

For the moment, I patch this problem deconnecting everybody on fix time and
then I compact the database. After that, users can access again.

I wonder if with an important data traffic, it may have an incompatibility
between DAO and access 2003.
If I ask this question is because the actual database is a migration from
access 97 to access 2003

If someone have an idea on this problem,

Thanks

 

[Arvin Meyer [MVP]]

Large amounts of data moving in and out of a database through an import and
export will do this until compacted. I have one database that imports about
35 to 40 MB of data every day, and it grows to over 100 MB. As I delete the
imported data it does not reduce the space required until compacted. I
typically set the Compact On Close property in Options to ensure it will be
done regularly. Using OLE fields, particularly of image data will also bloat
a database. Databases with embedded images do not reduce appreciably after
being compacted.