Size limit for Access 2003 database?

[Michael D]

I have an Access 2003 database that seems to be growing very quickly after
some development of new VBA code. It is a very automated database with a lot
of VBA code in both the forms, modules and some class modules. I have added
very little new data (only for testing) but after each session of code
development the file size is growing very quickly. It is currently just over
31Mb. I use the option to Compact on Close, so I can't understand why it is
suddenly growing so rapidly. Today I only added about 10kb of code text, but
the file size is approx. 1 Mb larger after this one session of development.
In fact once the file jumped over 20Mb in size about a week ago it seems to
be geting rapidly bigger each day even with minor code changes.

Is there a way of testing and cleaning out any junk which Microsoft Access
may add in to auto resize itself or other internal housekeeping procedures?

Thanks.

Michael D.
8 May 2007

 

[John W. Vinson]

I have an Access 2003 database that seems to be growing very quickly after
some development of new VBA code. It is a very automated database with a lot
of VBA code in both the forms, modules and some class modules. I have added
very little new data (only for testing) but after each session of code
development the file size is growing very quickly. It is currently just over
31Mb. I use the option to Compact on Close, so I can't understand why it is
suddenly growing so rapidly. Today I only added about 10kb of code text, but
the file size is approx. 1 Mb larger after this one session of development.
In fact once the file jumped over 20Mb in size about a week ago it seems to
be geting rapidly bigger each day even with minor code changes.

Is there a way of testing and cleaning out any junk which Microsoft Access
may add in to auto resize itself or other internal housekeeping procedures?

31 MByte is not at all large. The limit is 2048 MByte (2 GByte).

See the tips at http://www.granite.ab.ca/access for preventing corruption; it
is possible (and often valuable, after you *make a secure backup*) to
decompile your database, and occasionally even create a new database and
import everything; Compact does not clean out everything. I've also heard of
problems with Compact on Close; it's really probably preferable to compact
when needed, manually.

John W. Vinson [MVP]