Microsoft access 2003 disk or network error
Cancel Submit. Scottgem MVP. Access is very sensitive to network fluctuations. The problem is most likely your network infrastructure. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Daniel Pineault MVP. Also, it help us greatly if you post the error number as well as the actual error description. David W. Banana said:. Click to expand Tony Toews [MVP].
Baggott said:. John Spencer said:. It is happening on multiple workstations in both the front end and the back end in fact I can get a pretty good guess of who's in the database by how many shouts of, "Is something going on with the database? This just started up last Monday. There were no changes to the network or the workstations in the week preceding when the error started showing up.
Prevention how? Without knowing what's causing it, I don't see how to prevent it. I understand the frustration, but that's the unfortunate fact. I would absolutely love to trap the error and would share it gladly but AFAIK, it's not trappable, so you have to prevent it by monitoring the hardware for any faults as others have suggested and they've given you few leads to look into for identifying the cause. The front end is also stored on the server. The back end is also used as the administrative database, containing some functionality that the administrators use that the rest of the group has no business touching.
It's worked fine that way for years. Then this tells us that the problem is in the switch to which all the PCs connect to or the server or somewhere in between there. See if the IT department did anything a week ago. Including someone mucking about in the wiring closet. My main concern with giving everyone their own copy of the front end is keeping them all current.
I have enough trouble making sure they all have the correct shortcuts on their desktop. Is there an easy way to push changes to everybody's machine at once from my desk, or would I have to go from desk to desk to make any changes we have people on separate floors of the building.
If there is a way to make it automatic, that would be even better, as I have a memory like a seive. Rick A. Fenton said:. From what I've seen this is usually an intermittently flaky network. Trouble is there can be many causes. As far as I know that page and the linked pages are the most exhaustive collection of possible causes of corruption. The biggest problem will likely be convincing the IT department that they have a problem. They, and many ignorant folks on Stack Overflow, will mutter bad words against Access when it's really a hard to find problem on the network.
You'll need to recode certain portions of the frontend to make it work with SQL Server linked tables. I'm not going to elaborate as it would be to address that in a separate question. I suppose this isn't the solution you're looking for but I think it's the most sure-fire way to eliminate the error your getting. However, if you truly have network stability issues, you will likely have problems with SQL Server as well although I think it is slightly more forgiving when it comes to network hiccups because of it's architecture.
How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 10 years, 11 months ago. Active 10 years, 11 months ago. Viewed 11k times. I am searching for a solution for the dreaded error in MS Access. Improve this question.