Access 97 errors

A

AL

I am running Access 97 on both Windows 2k server and also on pc's that are
running windows xp sp1 and 2. I am getting an error such as "disk or network
error". We are not experiencing any problems with our network as we have
over 450 users that can access their files without issue. It is just a small
group of about 5 or 6 people that are having this problem while accessing
their databases from the network drive. Any help on this would be greatly
appreciated.
 
L

Lynn Trapp

Unfortunately, "disk or network error" is one of the most elusive errors
you will encounter with Access. It can be attributable to the smallest
problem. It could be the result of a bad NIC in the user's computer. Access
is much more sensitive to small problems in the network that other
applications and may encounter problems when nothing else does.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html
 
A

AL

I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
 
T

Tony Toews

AL said:
I am running Access 97 on both Windows 2k server and also on pc's that are
running windows xp sp1 and 2. I am getting an error such as "disk or network
error". We are not experiencing any problems with our network as we have
over 450 users that can access their files without issue. It is just a small
group of about 5 or 6 people that are having this problem while accessing
their databases from the network drive.
Click to expand...

However Access is the proverbial canary in a coal mine. Other apps
may work fine or have intermittent recoverable problems which you
wouldn't notice. For example when you save a Word document or Excel
spreadsheet do you notice if it takes a few extra seconds to recover
as Word or Excel retries the save.

Are any of these 450 users using Access on the file server?

Could these 5 or 6 people be on their own hub or switch that is
intermittently flaky?

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

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
 
L

Lynn Trapp

I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time.
Click to expand...

It doesn't take much of a hiccup with Access to get the error you described.
You might look into the possibility, that Tony suggested, that those 5 or 6
people are all on the same hub. Good luck getting the database converted.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
L

li chun yin

AL said:
I wish it were as simple as a bad NIC - but with 5 or 6 people all at one
time - some on pc's and some on citrix terminals, i dont think that is the
case at this time. we are trying to get the person that wrote these
databases to convert them to SQL, but havent had much luck - so we have to
deal with this crap for now. Thanks anyway.
Click to expand...
 
A

AL

Well fortunately i found a fix for my terminal server users on microsoft's
website that worked - no more problems with them, but i still have a couple
of users that are on pc's that are still receiving the error. its not a hub
issue because the users are located in different parts of the building on
different hubs. they can also access the terminal server connection through
their pc's - their terminal server connection is now running fine with no
more errors, but their pc will intermittenly give them the error.
 
T

Tony Toews

AL said:
Well fortunately i found a fix for my terminal server users on microsoft's
website that worked - no more problems with them,
Click to expand...

What was the fix? I'm curious because I like know what has worked for
folks.
but i still have a couple
of users that are on pc's that are still receiving the error. its not a hub
issue because the users are located in different parts of the building on
different hubs. they can also access the terminal server connection through
their pc's - their terminal server connection is now running fine with no
more errors, but their pc will intermittenly give them the error.
Click to expand...

Ok, the hub was a shot in the dark.

There are many other causes but it's been my experience that "disk or
network error" is hardware related. For example I had a laptop where
the network cable had to be snuggly inserted and/or wiggled a bit to
get a good connection.

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
 
S

Simon Westenra

Tony Toews said:
What was the fix? I'm curious because I like know what has worked for
folks.
Click to expand...

Too right. Tell me what the Fix was.
Our Access 97 databases are still getting corrupt on our Citrix environment
after we've moved then to Access XP, split them, ensured given each user a
copy of the front end, added in an auto-timeout to close it down, told them
to limit the number of users to a maximum of 6 and moved the database to a
better server (off an old Novell box) and ensured that Opportunistic Locking
is disabled.

We get Disk or Network Errorintermittantly. Fortunately it only affects one
user, as they can close their session down and fire up another copy of the
front end. But is still a nuisance.
Cheers
Simon Westenra
Capital&Coast Health, Wellington, NZ.
 
Top