MS Access Disk or Network Error 3043

I am searching for a solution for the dreaded 3043 error in MS Access.

One of my clients is running a splitted FE/BE application, about 6-7 users, BE size about 100 MB. In the last weeks the error is coming more and more often. After closing the DB and reopening everything is just fine. But the data entered in the currently open form is lost. At first this happened once a day, now every 90 minutes - which is very annoying for the users.

The web is full of possible solutions a开发者_C百科nd workarounds, but nothing really works or helps to clear this issue.

From what I've seen this is usually an intermittently flaky network. Trouble is there can be many causes. You've probably already seen my Corrupt Microsoft Access MDBs FAQ page. 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.

Consider converting the backend to SQL Server 2008 Express and then use ODBC linked tables to connect the front end to the backend. 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.)

Microsoft has a free tool you can use to convert your database backend to SQL Server: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5abe098d-c7e1-46c6-994a-09a2856eef0b&displaylang=en

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.