Microsoft Access - "Disk or Network Error"

G

GLK_Jeff

Ever since I installed Microsoft Windows XP Service Pack 2 a few weeks ago,
we have been having problems with a simple Microsoft Access database I
developed 7 years ago in Access 97, and eventually was converted to Access
2002 3 years ago. The database was working fine without any problems until I
installed Service Pack 2.

Background:

The database is located on one computer's harddrive, and 5 other computers
are using the database via a basic peer-to-peer network using a fast Ethernet
switch. We are all using Microsoft Windows XP Professional and Microsoft
Office XP. I have installed Windows XP Service Pack 2 on 3 of the 5
computers using the database, but the problem is occurring on all 5 of the
computers that use the database (it doesn't happen on the computer that has
the database on its harddrive). The machines were purchased brand new from
Dell 2.5 years ago, and are the Dimension 4400 series.

Problem:

For no apparent reason, a computer can get arbitrarily kicked out of the
database, with the error message "Disk or network error", and the person on
that computer must click on that error message many times and then exit out
of Access and get back into the database. It happens every day on some
machines, only every several days on others. The only pattern I can see is
that it happens within the first 10 to 15 minutes of booting up, then once
you click off all the error messages and exit out and get back into the
database, for the rest of the day, it is fine. It has never happened on the
computer that has the database on its harddrive.

Please help - this is frustrating and affecting our productivity. I love
Microsoft products, and I actually have my own computer consulting business
that uses strictly Access (and sometimes SQL Server as a back end), however,
I need to get this conflict with SP2 resolved. On my home machine, I
installed SP2, and now one of my USB devices won't work, and apparently
Microsoft has acknowledged that to be a problem. The device doesn’t have an
external power supply, so I am pretty much stuck with the option of
uninstalling SP2 in order to use the device, but I doubt Microsoft would
recommend that. I am only bringing this up to give you an example of another
problem I had with SP2, and from what I have read, others are having some
problems also.

Thanks for your help on the database issue outlined above.
 
S

Sylvain Lafontaine

Did you try to recompile your database with the /recompile option and check
for the latest version in the references window?

S. L.
 
A

Albert D. Kallal

GLK_Jeff said:
Problem:

For no apparent reason, a computer can get arbitrarily kicked out of the
database, with the error message "Disk or network error", and the person
on
that computer must click on that error message many times and then exit
out
of Access and get back into the database.

A LOT of people are running SP2, and I not seen any new information that
would cause the above..at least in the ms-access newsgroups..and we get
about 1000 posts a day in the ms-access areas. I have seen some a97
applications break on pc's that have 2, or even 3 versions of access
installed..but for the most part the sp2 has not effected ms-access very
often.

However, a few things to check:

Are you running a split database? For any multi-user ms-access stuff, you as
rule need to be running a split database. The reason here is that one miss
behaving computer will thus not bring the down whole application. And, each
workstation should in fact have a mde..and not a mdb. And, you might want to
test/check if your code compiles as it is now. You can read up on splitting
here:

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

The above splitting may not solve your current problems..but it usually
results in a MUCH more reliable situation. And, thus if one pc has a
problem, then all pc's don't get this problem. It is very possible that some
references are a issue here also. If you go and fix this reference on one
pc..then all others can be effected. So, again having a copy of the
application (mde) on each pc linked to the back end mdb file that sits in
the shared folder is the way to go here.
It happens every day on some
machines, only every several days on others. The only pattern I can see
is
that it happens within the first 10 to 15 minutes of booting up, then once
you click off all the error messages and exit out and get back into the
database, for the rest of the day, it is fine. It has never happened on
the
computer that has the database on its harddrive.

Do you share the folder via a unc path name, or do you use a mapped drive
(this is bad!!). Sometimes, those mapped drives don't re-connect properly at
a logon. Only AFTER you try to use a file, does the network connection take.
(and, you seem to hint once the connection happens...then it stays). In
other words, does that shared folder have any restrictions? I would also use
unc path names in placed of mapped drives..as that might also help. And,
what kind of security settings do you have for this shared folder..
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top