Steve Capistrant
scapistrant at symphonyinfo.com
Tue Mar 8 09:15:36 CST 2005
John, I like the elegance of that solution, since our "compact on close" routine takes time and really fouls up users who exit and try immediately to reenter. However, our FE files usually carry a number of user-defined settings (preferences, defaults, etc), and these get wiped out with upgrades, so your system of daily refreshes would be a problem. But now I'm wondering if we could store the user-defined settings outside of the FE...perhaps in a text file, or a little companion mdb. Have you tried this? Steve Capistrant scapistrant at symphonyinfo.com Symphony Information Services 7308 Aspen Lane North, Suite 132 Brooklyn Park, MN 55428 763-391-7400 www.symphonyinfo.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Colby Sent: Tuesday, March 08, 2005 9:00 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Learned something new Steve, that is certainly possible to do. If you set up your systems such that the FE is downloaded to the workstation daily so that users get the latest version whenever fixes are applied, then you no longer need to worry about bloating since the FE isn't around long enough to bloat. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Tuesday, March 08, 2005 9:41 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Learned something new What is your work database? A separate dedicated to handling temp tables? Does your FE have permanent links to permanent tables in that work db? Does your FE's linking tool manage two sets of links -- to the BE and the WorkDb? Steve Capistrant scapistrant at symphonyinfo.com Symphony Information Services 7308 Aspen Lane North, Suite 132 Brooklyn Park, MN 55428 763-391-7400 www.symphonyinfo.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bobby Heid Sent: Tuesday, March 08, 2005 6:30 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Learned something new I always use a "work" database, that is separate from the FE, but in the same location. I then compact it upon exiting the application. Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, Karen Sent: Tuesday, March 08, 2005 6:46 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Learned something new I use temp tables for similar purposes, but they bloat the database a bit, so I code it in to compact the puppy. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com