| Larry Linson 2006-03-17, 8:33 pm |
| My experience is that a T-1 line is at the very low-end of acceptable
communication speed for an Access multiuser database. I have been able to
tell the difference between old 4MPBS networks and 10MBPS networks on the
same database.
Yes, Access is very sensitive to network difficulties. It's not so much that
Access "finds" the problem; it's that Access just doesn't work when there is
such a problem.
I'd say you need to visit MVP Tony Toews' site, http://www.granite.ab.ca,
because he has about the most extensive collection of information and links
on multiuser performance and corruption-avoidance that I have found. You
might find a few different links and items at Jeff Conrad's site,
http://home.bendbroadband.com/conra...cessjunkie.html
Larry Linson
Microsoft Access MVP
<Jpetrachkoff@neo.rr.com> wrote in message
news:1142602861.246881.140440@j52g2000cwj.googlegroups.com...
> For the past 9 years we have had a database (split) .Server 2000. Two
> buildings (One server) T1 line connecting the two. The building
> farthest away has now started giving disk or network errors.
> The network administrator says it is the database. I disagree.
> Also it used to be multiple users at the far away building could get
> into the program at the same time. Now if one is in it and another
> tries it will create the error.
> The system administrator 'pings' the server I noticed a 'timeout' then
> a connection. I am aware access is senstive to network bugs and will
> find them, but it won't tell me what the bug is...
>
|