Disk or Network Error

[dots]

I created a new Access database and put it on our network drive. All users have Access 97 and Windows 98.

One user (the one that critically needs to use this database of course) can open the database, and use it until they click on any command button. When they do that, they receive an error message (after several minutes delay) "Disk or Network Error". After that, they have to Ctrl-Alt-Del to get out of the application as it freezes up.

I have tried the application on many different workstations, and no one else has this problem.

I thought it might be the network card (although they have no problem with any other applications), so I replaced it to no avail.

Has anyone ever experienced this? Can anyone suggest anything to correct it?

By the way, the database is not split. Could this be the problem?

Thanks for any help, or advice you can send my way.

Dorothy

 

[sha76]

Does the user have this problem with other databases? If so you may want to try re-installing Access.

Sharon

 

[dots]

Thanks, I'll have him try some other databases.

 

[PCSAARON]

We have the same problem with our access database. This trouble has been hounding us for years now. If we reboot the machine and try again, it usually helps. It is intermittent though. We have one machine on the network that works EVERY time. There is no differences in the hardware or software.

One of our clients had a small access front end database that was split and the tables were kept on a window 98 machine. One or two machines kept getting a disk or network error. It was a junky machine. We replaced the "realtek" cards with 3Com cards and it solved the problem.

Note: I read somewhere that realtek had a few known problems with the tcp/ip stack. This is when I had the idea to replace the cards with 3com's.

I replaced one of the machine's network cards to a 3com that had the disk or network errors and it didn't seem to help on our database. We did check the wiring with our EXPENSIVE Fluke network tester/certifier. All wiring is fine. I do know that the one workstation that is fine has been replaced several times with different equiopment and it is still working great, and this may have nothing to do with it, but it IS the closet machine to the server... This should have nothing to do with it, but it is either that or gremlins!

Microsoft DOES have issue with Access and network use. Everyone has problems. This is why we are currently changing our access database over to MySQL. NO more problems and it is quicker and more efficient.

I hope this helps, I don't think there is a solution besides DROPPING access...

Aaron

 

[psemianonymous]

The corrupt MDBs FAQ (link below) says not to store files on a Windows98/ME/95 machine if the clients are using NT-based OS's. Consider the possibility that it is unwise to host backend MDB's on a 95/DOS-based operating system. Consider (if you have one available) moving the file to an NT-based file server.

Also linked to by the FAQ are a "good practices" page:

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q300216

No one has mentioned yet--have you upgraded to the Access service packs? It's one of the items listed in the "good practices".

Anyway. Something to think about.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

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