Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / February 2005

Tip: Looking for answers? Try searching our database.

Slow Load Time of Forms

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Weste - 15 Feb 2005 22:41 GMT
I have a multi-user Access 97 database.  The database is split into a FE and
BE.  There are about 25 concurrent users.  We are experiencing some speed
issues and I think it is mostly network related but I am not sure how to
prove it.  For example, there is a form with a subform.  The main form has
approx 23 controls and the subform has about 23 controls.  The maximum number
of records the main form returns is 1.  The maximum number of records the
subform returns is 52.  When I access the form with the BE on my local pc, it
loads in 0-1 second.  When the form is accessed with the BE on the network it
loads anywhere from 2-131 seconds.  Why the big difference in the load time?  
The user already has a connection to the database table when this form is
loaded.   I know the number of users effects performance but some of the
longer load times only has a handful of users in the database.  The local pcs
are configured at 10 Mbps.  If it was a form design issue, then wouldn’t the
load time be long for all users?  Is there a way to isolate if this is indeed
a network issue.  Any assistance is greatly appreciated.  Thanks.
Albert D. Kallal - 18 Feb 2005 00:28 GMT
>The user already has a connection to the database table when this form is
loaded.

What *EXACTLY* do you mean by the above?

I am going to suggest you try the following:
Make sure in your start up form, or startup code, you open a table to the BE
and KEEP it open. That means we want to keep a PERSISTENT connection OPEN
to the back end.

AFTER  a you have the persistent connection open, and function as part of
your application, you CAN NOW try running/launching that form to the one
record. Your delay should go away.

>I have a multi-user Access 97 database.  The database is split into a FE
>and
> BE.

Good, I assume the FE is on EACH pc..right??

>The local pcs
> are configured at 10 Mbps.

Well, a cheap standard office network is usually rated at 100. And, a hard
disk is several times faster then the cheap 100 mbits network.

So, lets pretend that the hard disk is about 4 times faster then the 100
mbits network.

So, you got:

10 mbits * 10 = 100 mbits

And, we are saying 4 times faster for the hard disk over the 100 mbits
network.

so, * 4 for the hard disk comparison.

= 400 times slower

So, you are basically explaining to me that you go two situations, and the
2nd situation is about 400 times slower then the first. I not sure what much
I can teach you in terms of math here, but it does sound like the speed of
your network is about 400 times slower then that of your local hard disk.

Anyway, MAKE SURE you try the persistent connection here.

Also, are you taking about a standard office LAN, or are you talking about a
wan?

If you are taking about a wide area network, then read the following for
some solutions:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

However, try the persistant trick..as it often does fix very large delays...

Signature

Albert D. Kallal   (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.members.shaw.ca/AlbertKallal

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.