disk or network error

  • Thread starter Thread starter frans van Ek
  • Start date Start date
F

frans van Ek

Hi

I keep on getting an Disk or network error while working
in a access database. when i start te db there is no
problem. Has anyone an idea what can case this problem ?

the operating system is windows xp

thanks in advance

frans
 
frans van Ek said:
I keep on getting an Disk or network error while working
in a access database. when i start te db there is no
problem. Has anyone an idea what can case this problem ?
Click to expand...

I'm going to disagree with Arvin in your situation. If this problem
occurred when you first opened your database then it could very well
be a temp file problem. However you're getting this message while
working in the database.

This is likely caused by an intermittent hardware problem such as a
loose cable connection or flaky power and the network hub/switch is
not on a UPS.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
A loose connection remains the most likely cause but I have experienced this
on several occasions:

1) This almost never occurs if you have Access fronting an SQL database -
MDB's seem much more susceptible.
2) Make sure the database is compacted and as small as possible. My
experience is that the bigger the MDB file, the more likely is the error.
3) The problem is even more likely if you are sharing an MDB with several
users over a network.

If possible, forget Access as a shared DB, use SQL 2000 or MSDE 2000 for the
back-end and this class of error (assuming it is not caused by hardware)
will disappear.

HTH

Paul
 
Velociraptor said:
A loose connection remains the most likely cause but I have experienced this
on several occasions:

1) This almost never occurs if you have Access fronting an SQL database -
MDB's seem much more susceptible.
Click to expand...

Absolutely. One reason would be because there is much less network
traffic. Another is that Access sends a small amount of constant
network traffic every second. When dealing with SQL Server it likely
doesn't.
2) Make sure the database is compacted and as small as possible. My
experience is that the bigger the MDB file, the more likely is the error.
Sure.

3) The problem is even more likely if you are sharing an MDB with several
users over a network.
Why?

If possible, forget Access as a shared DB, use SQL 2000 or MSDE 2000 for the
back-end and this class of error (assuming it is not caused by hardware)
will disappear.
Click to expand...

Sure. but SQL Server is more work to install and learn. There can
also be a very significant investment in time to convert from an
Access BE to SQL Server.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Another issue that you can run into with Novel is record locking.
This will let everyone into database, but if record locks are not set high
enough...
there are 2 settings: individual & global.
i found that the error was NOT indicitive of the problem - or at least not
clear.

we had queries that would run - if we limited the number of records.
----------------
another thing that just hit us, we have some older wire (cat3) our hub was
upgraded to a 100 Mb switch. and the users workstations were set to
autodetect. they tried to run at 100 and were creating all kinds of extra
traffic. the others are suggesting a flaky connection - it may be a flaky
electronicly or protocol wise, but still good physicly.
 
Back
Top