[AccessD] Compact and Repair on Close

The main reason for compact on close in FEs is to get rid of the bloat
caused by running queries, running reports (which runs additional
queries), and all the temporary queries Access plays with behind the
scenes.   

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
at Beach Access Software
Sent: Monday, December 31, 2007 5:34 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Compact and Repair on Close

	 
Dear List:
 
I have a legacy app that was set up to compact and repair on close.  I
found it annoying during development - the delay every time I closed and
re-opened the app.  So I disabled it.  The program will eventually
become an mde and will be distributed to a vertical market.
 
Q: is there any reason to C&R on exit?  I know it gets rid of the
'bloat' - but IME that bloat is mostly inconsequential in terms of
execution time.
There are very few front end tables in this app - it's all back end.  Or
is there some other good reason to turn this C&R on Exit feature back
on?
 
MTIA
 
Rocky
 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com