Causes of front-end bloat besides not .Closing Recordsets/QueryDefs?

[(Pete Cresswell)]

I've got a front end that manages to grow itself from about 5 megs to over 100
megs in the course of a 8-10 hour batch job that performs something over a
million calculations.

I've stepped through the code twice now - looking for DAO.RecordSets and
DAO.QueryDefs that are not .Closed and Set = Nothing; but have not been able to
find anything.

Can anybody suggest any other cause of bloating?

In this app:
-----------------------------------------------
- No work tables are created within same.
- No links are created/deleted/modified in the course of the batch job.
- No queries are created/deleted by the app.
- No data whatsoever is stored in the app at any time.
- No objects (that I know of....) are modified.
- There are no graphic images at all in this front end (or, for that matter, the
back end...)
----------------------------------------------

One thing I *do* do, however is to open up various QueryDefs, feed them
parameters, and then open recordsets based on same. But as far as I can see,
everything is .Closed after use and Set = Nothing.

Doesn't seem to me like that constitutes modifying the QueryDefs - and I've done
about a quarter million iterations of that in a little test app with no
bloat....but maybe I'm missing something.


Occam suggests that I'm just lying about the .Closes.... and maybe I'll find
something tomorrow morning when I step through it for a third time...

Meanwhile....?

 

[(Pete Cresswell)]

Per (Pete Cresswell):

Meanwhile

It's an MS Access 2003 app - using 2003 DB format in both front and back end.

 

[Dave]

Per (Pete Cresswell):

It's an MS Access 2003 app - using 2003 DB format in both front and back end.

bloat is normal. if you are making temp tables or adding/deleting records
or lots of other stuff the space used does not get reclaimed until you
compact the database... so the longer you run, the bigger the file gets in
most cases... its not like a memory leak, its more like garbage collection
that only gets done manually.

 

[Roy Ristie]

Hi, think about what's happening. Inorder to make the data from the be
available in the fe it must be fetched and temporarily stored in the fe.
You say that it's a batch job so I assume you're processing lots of data
thus lots of temp storage is used. Access leaves it up to you to cleanup
after it, ie. compress the fe.
I may be wrong but logically something like the above must happen in the
exchange od data between be and fe.

HTH
Roy

 

[(Pete Cresswell)]

Per Dave:

bloat is normal. if you are making temp tables or adding/deleting records
or lots of other stuff the space used does not get reclaimed until you
compact the database.

No temp tables in the FE, no data in the FE.