[AccessD] Locking question

Bobby Heid bheid at appdevgrp.com
Wed Jul 27 14:05:57 CDT 2005


It turns out that there is not a real problem other than the users are being
impatient.  The app has gotten bloated over time and needs to be rewritten
with SQL server, but the client does not want to do that yet.

The app is a little slow loading, especially on the network they are on.
They are having network problems which is slowing the app way down.  On my
slow machine (700Mhz PIII), it takes about 2 seconds to load the database
from a local drive.  It is taking them about 1-1.5 minutes to load.

As for the question about relinking at startup, we tried not relinking
before.  But there always seemed to be issues with that.  So it was decided
to just relink each time.

Thanks for the replies,
Bobby

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: Wednesday, July 27, 2005 2:40 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Locking question


Just a thought: if it really is related to the re-linking process, then why
not have the app. simply check the links, and only do a re-link if needed?

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bobby Heid
Sent: Wednesday, July 27, 2005 2:17 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Locking question


Hey,

Our clients use our system on a network where each user has a FE against the
BE on the server.  While the app was originally written to all be on the
local pc, it has migrated to the server.  Usually all goes well.

Well, this one client has some weird happenings going on.  One user will be
in the database in any given form.  Another user cannot get access to the BE
until the 1st user exits the form they were in.  The first thing the app
does is to relink the tables to the last BE that was loaded.  It sounds like
there are some sort of issues with locking and the LDB file.  

Anyone have any pointers?

Thanks,
Bobby





More information about the AccessD mailing list