jwcolby
jwcolby at colbyconsulting.com
Fri Jan 30 15:41:56 CST 2009
>If so it should only be the IT guy. Not at all. What you need to do is hold a table open to the be. The slowness is caused by obtaining and releasing the lock to the BE for every table relinked. Open a small table and hold it open, then do the relink. It should be fast then. John W. Colby www.ColbyConsulting.com Dan Waters wrote: > Good point - I'll have to ask if someone has the BE open. If so it should > only be the IT guy. > > Thanks! > Dan > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel > Sent: Friday, January 30, 2009 3:08 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Very slow table link refreshing > > Dan, > > I have found that relinking is very fast if that machine is the only one > connected to the backend at the time. Relinking if the backend is already > opened from another workstation is always much slower. Does this apply in > your situation? > > Regards > Steve > > From: Dan Waters > Sent: Saturday, January 31, 2009 10:04 AM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] Very slow table link refreshing > > > Hello to everyone! > > At one of my customer's sites, they have seen sometimes where table links > in > the Access 2000 FE refresh the links very slowly to the Access 2000 BE > tables on the server. I've also seen this while I've been remotely logged > in to the server and tried refreshing the table links from a FE to a BE. > > Normally this refreshing takes about 2-3 seconds for about 20 tables. But > I > timed this at 4 minutes one day. CPU usage on the server was effectively > 0 > at the time, and the maximum possible client connection is only 4. Later > that day we were back to about 2 seconds. > > I would like to know anyone has any thoughts on what I can look for in my > system, or anything I can pass on to the IT guy for him to look at? >