Network Disk Error

  • Thread starter Thread starter SueG
  • Start date Start date
S

SueG

I have an Access 2003 database that the users keep
getting a network disk error. To get it to work, the
users have to close the database and reopen it. If this
happened occassionally, I would not be concerned but it
is happening almost every time they go into the database.
Through researching this I have done some of the
suggestions like changing the subdatasheets of the
backend to none, deleting the links and recreating them,
and even playing with some of the options...but none of
this helps. This database had absolutely no problems in
Access 97, but now in 2003 is horrible. It is tough to
convince the user community that upgrading was a good
thing when they keep losing work and getting
disconnected. Does anyone have any ideas??

Sue
 
SueG said:
I have an Access 2003 database that the users keep
getting a network disk error. To get it to work, the
users have to close the database and reopen it. If this
happened occassionally, I would not be concerned but it
is happening almost every time they go into the database.
Through researching this I have done some of the
suggestions like changing the subdatasheets of the
backend to none, deleting the links and recreating them,
and even playing with some of the options...but none of
this helps. This database had absolutely no problems in
Access 97, but now in 2003 is horrible. It is tough to
convince the user community that upgrading was a good
thing when they keep losing work and getting
disconnected. Does anyone have any ideas??

Sue
Click to expand...
Have your network people check the network. This could be a timeout problem
with the answer not getting back to the requesting computer on time.
Also it could be a hardware problem in a network Interface Card (NIC).
You didn't say if you upgraded the computer(s) or the OS. Sometimes
upgrading
software without upgrading the hardware will cause things to slow down.
This
could be the cause of a timeout problem, if timing is what's causing
your problem.


Ron
 
Hi SueG,

Since you can reproduce the error almost at will, have you tried eliminating
the network by running everything on a local drive? Is this feasible?
I would also make sure you all the workstations have the latest Service
Packs.

Immanuel Sibero
 
Back
Top