Heenan, Lambert
Lambert.Heenan at AIG.com
Mon May 15 12:41:19 CDT 2006
Your boss maybe needs to consider where 'facts' come form. :-) The most important source is empirical testing. Here's a fact for him: Been running various Access applications for 10 year, in both Access 97 and 2002. Never needed to relink any tables at startup. Why might you need to do so? 1/ The drive mappings on a user's system might change, making the backend seem to have disappeared. Solution? Use UNC path not drive mappings. 2/ The backend might have been moved to a different file server, so the UNC path does not point to it any more. Solution? Develop a relationship with the network managers so you'll know in advance if things are going to move. HTH Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bobby Heid Sent: Monday, May 15, 2006 1:09 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] [SPAM SUSPECT] Re: To re-link or not to re-link... Hi Gustav, That is what I was suggesting we do. But my boss wanted facts. Thanks, Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Monday, May 15, 2006 12:09 PM To: accessd at databaseadvisors.com Subject: [SPAM SUSPECT] Re: [AccessD] To re-link or not to re-link... Importance: Low Hi Bobby We've never (since and including Access 2.0) seen any issues by _not_ relinking at every launch of the app. That's for JET tables. Neither have I seen such a need for SQL Server. It may be different for other (ODBC connected) engines though. Why not just disable the relinking and watch what happens? /gustav >>> bheid at appdevgrp.com 15-05-2006 17:33 >>> Hey, We have a system that was originally developed in Access 97. There were a number of tables that were linked to the FE. There were issues (not sure what they were as no one remembers and I did not write the original) with the system if the tables were not re-linked each time the system is loaded. Well, here we are today and the app has grown into Access XP. The system has grown and now has over 100 tables. As such, it takes about .6 seconds per table to re-link them all. Does anyone know what the issues may have been before and if they still exist in Access XP? Anyone have any pointers to further information? Thanks, Bobby -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com