MDB bloat - a few questions

Question

In a newly deployed split database, the front end has gone from 1.5 to 11 MB in one week. Not a problem, but it will be if it increases 10MB per week! This has raised some questions:

In a split database, will bloat always occur in the front end, or either?
Other that being sure to close recordsets, and set them to nothing, are there any specific suggestions to avoid bloat?
Will queries defined in code bloat more than saved ones? I know they are slower, but what about bloat?

Answer

From: Shamil Salakhetdinov <shamil@marta.darts.spb.ru>
To: ACCESS-L <ACCESS-L@PEACH.EASE.LSOFT.COM>
Subject: Re: Bloat - a few questions..
Date: 19 February 1999 1:50

Peter,

I did some investigations several months ago and I found that properly
designed and programmed MS Access app with one or more front-ends and one or
more back-ends can bloat slightly only when you reattach tables...

- Temporary queries don't bloat mdb size
- Parameterized queries (when used) don't bloat mdb size
- Temp tables should be stored in temp back-end local mdb(s)
- MS Access 97 *does* reuse mdbs pages
- The execution speed difference between stored queries and queries built by
VBA code on-the-fly is so little you can neglect it
- On-the-fly built queries could be faster in fact - as far as I understand
MSAcc97 creates query plan when it compiles query (compacts mdb?) -
therefore on-the-fly queries are always up-to-date and usually faster (?)
than saved ones!???
- But you'd better use saved (action) queries not because of the fact that
they are faster but becase of the fact that this is the only way to use
OWNER ACCESS OPTION for action queries...
...

Could you please point me the real life app's case which does not have
satisfactory workaround avoiding front-end mdb bloating?
Probably I did mistake(s) in my investigations - don't hesitate to point on
them/recheck...

HTH,
Shamil