databases that grow like cabbage

[WindAndWaves]

My Front End used to be around the 30megabyte, now it is 60 megabyte....
this change occured almost overnight and I have done the compress thing many
time (I am running MS Office 2003).

When I ran a couple of procedures, it went up to 1.3 gig!

I quickly compressed and we went back to 60 megabyte. But surely this could
be smaller.

Has anyone experienced anything like that??? And what can be done about it?

TIA

- Nicolaas

[Larry Linson]

There are quite a number of things that can cause bloat... one that is often
a big contributor is the use of temporary tables; some queries create
internal workspace that isn't recovered. For a fix to the temporary tables
problem, if you have it, see MVP Tony Toews' website,
http://www.granite.ab.ca/accsmstr.htm for his example of creating a
temporary database to contain the temporary tables. Another, but less
likely, problem can be due to creating objects with Set and not Setting them
to Nothing before they go out of scope. Googling the archives here should be
productive... http://groups.google.com.

Larry Linson
Microsoft Access MVP

"WindAndWaves" <ac****@ngaru.com> wrote in message
news:m1******************@news.xtra.co.nz...

My Front End used to be around the 30megabyte, now it is 60 megabyte....
this change occured almost overnight and I have done the compress thing many time (I am running MS Office 2003).

When I ran a couple of procedures, it went up to 1.3 gig!

I quickly compressed and we went back to 60 megabyte. But surely this could be smaller.

Has anyone experienced anything like that??? And what can be done about it?
TIA

- Nicolaas