DataBase - Very Odd Linking issue

Asked By gcoggin

23-Sep-09 06:27 PM

Howdy,

I have two database applications that use the FE/BE model over a p2p network.
One of them works great. It loads quickly and the forms open with very little
delay.

The second one loads OK but everything opens very slowly. Even just opening a
linked table takes 6 or 8 seconds. I use some code to relink the tables for
when I am doing development. When I link to the production folder on the
backend in another folder on the same machine it takes 10 seconds and the
tables and everything open almost instantly. Ironically, the folder that
connects quicker has about 15 more characters in the path than the
troublesome one though they are same number of folders from root. The
confusing issue for me is that the same files behave so differently in
different locations.

I have checked that all the permissions are the same. Does anyone have any
suggestions for what I can look at that might cause one folder to work well
and the other one not to?

Any suggestions will be greatly appreciated.

Thanks.

23-Sep-09 09:44 PM

Go to Tony's site on this "Access 2000/Windows 2000-Slow Performance....kind
of solved"

http://www.granite.ab.ca/access/performancefaq.htm

Taken from site.
'------------------------------------------------------------
PB stated that shortening the path from 75 characters to 31 characters and
removing four directory levels changed "from 50 seconds to load for the first
time and was accelerated to unbelievable about 15 seconds." "About 3 1/2s
instead of 15s is a real progress."  They also shortened the name of the back
end.
'-----------------------------------------------------------


--
Please Rate the posting if helps you.

Message posted via http://www.accessmonster.com

23-Sep-09 11:21 PM

What do you mean by p2p network?  Peer to peer?  Is this in the same
office or are they separated geographically?


Are these both on the same computers?  That is the both FEs are on
your PC and both BEs are on the same other PC?


What do you mean by different locations?  Different folders on the
same server?

Now was someone else using the second slower app at the same time you
were using it?  And no one was in the first app?  If so that is the LDB
locking issue where a database variable, recordset variable or bound
form helps.  Also if relinking the tables either open a database
variable to the BE or, once you are relinked the first table, open a
recordset variable against that table.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/

31-Oct-09 10:04 AM

Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,