Don't you think it would be easier just to compact when you're done deleting
rows?
Chris
Microsoft MVP
DS wrote:
>I'm running SQL statements to delete unwanted records.
>Is there a way to do this without bloating each time a deletion is run?
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200810/1
Unless your SQL is very peculiar, deleting records will leave the size of the
database unchanged. It won't *cause* bloat. The only thing that it will *not*
do is free up the space formerly occupied by the deleted records.
If you want to free up that space, then yes, you will need to compact.
If you are using a temp table or a "scratchpad" table (routinely filled and
emptied) consider putting it in a separate backend. You can create a new .mdb
file for the table at the start of the process, and Kill it when done.
--
John W. Vinson [MVP]
Exactly. That space is marked as used and not reused until you compact.
>Thanks John. I am using these tables to update and move records. I like
>the idea of a seperate database!
See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/