Sahar said:
Yes, that is what I normally do. After I compact the new database, it is
about 40MB, but what causes it get so large? It happens daily to the database.
One thing I'd do is ensure everyone is running the same version of
Jet.
What I've done is use the various API calls available and am checking
the version number and date/time of a crucial dll, msjetxx.dll, to
ensure it matches what I have on my system. See the Verify
Appropriate Jet Service Pack is installed page at my website for more
details including sample code:
www.granite.ab.ca\access\verifyjetsp.htm
If however the problem is extensive use of temporary tables or
importing and discarding large numbers of records then I'd use a
temporary MDB to store these.
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