Hello All,
Is there any fix to apparent MDB file size bloat when creating data
through the manipulation of recordsets in VB?
I'm trying to create sample data by manipulating the raw data set
using recordsets, the random number generator, and running append
queries in VB. I notice the MDB file is bloated. Granted I'm running
some delete queries, but it appears to occur most significantly when
editing recordsets by replacing nulls with data. I know I can run a
compact on the DB, but this requires disrupting the processing stream.
I have closed my recordsets, and set my db = nothing.
I did some Googling and found info that doesn't really help.
http://groups.google.com/groups?q=si...2005&safe=off&
From http://www.mvps.org/access/general/gen0041.htm
I can call this function at the end of code:
Public Sub CompactDB()
CommandBars("Menu Bar"). _
Controls("Tools"). _
Controls("Database utilities"). _
Controls("Compact and repair database..."). _
accDoDefaultAction
End Sub
Is there any general rules to avoid in code to minimize this bloat
effect, gotcha's, or am I just stuck with running the compact function
at the end of code and interrupting the process?
Any ideals, or do I have to live with it. TIA!
--
Regards,
Greg Strong