[AccessD] To re-link or not to re-link...

Jim DeMarco Jdemarco at hudsonhealthplan.org
Tue May 16 07:37:27 CDT 2006


This is the technique I subscribe to.  If your tables are in more than
one BE test the link to one table in each BE.  That's enough to know
there's an issue.  If an issue is discovered remember to take the advice
in other messages in this thread to keep an open connection to a table
to speed up relinking.

Jim DeMarco 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kath Pelletti
Sent: Monday, May 15, 2006 7:10 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] To re-link or not to re-link...

I think that re-linking to just one table is a good idea if you have
only one BE file. If you get the first link then you know that the BE
has been successfully located and you can bail out from there.

Kath
  ----- Original Message -----
  From: MartyConnelly
  To: Access Developers discussion and problem solving
  Sent: Tuesday, May 16, 2006 3:40 AM
  Subject: Re: [AccessD] To re-link or not to re-link...


  When re-linking try to keep one table open during relink process to
avoid
   opening and closing ldb file, remove subdatasheets on backend tables.
  Once the first table has been refreshed, open a recordset based on
that
  table.
  Continue refreshing. Once finished refreshing close the recordset
after
  you've opened a bound form (perhaps hidden) for performance reasons
  <../performancefaq.htm>.
  Performance FAQ's
  See
  http://www.granite.ab.ca/access/performanceldblocking.htm
  and also
  http://www.granite.ab.ca/access/performancefaq.htm


  Bobby Heid wrote:

  >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
  >
  >
  >

  --
  Marty Connelly
  Victoria, B.C.
  Canada

  --
  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



More information about the AccessD mailing list