Access failing over slow network

  • Thread starter Thread starter Digital Carnage
  • Start date Start date
D

Digital Carnage

Hi Gang,
I have an Access 2002 database that I've saved to a server's I:\ drive
and created a shortcut to the database on my client's workstation. They've
had some real bad network bandwidth issues which is creating severe lag
times when using any of my forms or even just opening the database. Forms
that worked just fine before and have not been altered are now return VB
error messages, returning false or no data to subforms and more. Is this a
common occurance for Access when response times are lagging over 1 minute or
more? Thanks Rich
 
If this is a multi-user database, you need to split it into a
Front-end/back-end solution, with a copy of the FE on each users machine.
That will reduce network traffic somewhat.

When you refer to the nework, is this a LAN or a WAN?

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm
 
For issues of connection performance, you want to check out:

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


Also...if you plan to have more then one user on the system, then you want
to use a split database arrangement. This also allows you to develop your
software in a far more controlled fashion.

For info on splitting..check out:

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

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm


Also, you are talking about a typical office network (a lan), and surely are
not talking about a wan...are you? You did ask how fast the network
is...right?

If you need information on connecting ms-access via a wan (wide area
network), then you can read the following article of mine:

http://www.attcanada.net/~kallal.msn/Wan/Wans.html
 
Kevin,
It's the State of Alaska so I'm assuming it's a WAN. However, there is
only 1 workstation that ever accesses this database, no one else. We put it
on the server so that it's backed up daily, that's the only reason. Other
documents and files are also taking forever to open on this network, not
just the database. A month ago before the network issues came about, these
forms worked absolutely great! So the only deduction I have left to
consider is some kind of timing out issue that Access doesn't like. Any
additional thoughts? Rich
 
I've seen access working with 0.5 hour response time
(access 2.0) and 5 minute response time (access 97),
but those were earlier versions.

Can you get Terminal Server working on the Server?

(david)
 
Back
Top