MA Access Database Issues

jonesda

Registered User.
Local time
Today, 14:45
Joined
Sep 13, 2005
Messages
36
MS Access Database Issues

Hi,

We have been having problems with MS Access for a few weeks now (MS Access front end to a SQL Server 2000 database). We have a shared .mde file which is in a network folder and used by 14 users. All users use MS Access 2000. Recently users have intermittently been getting error messages:
- Network or Disk Error
- Error executing the command
- You have cancelled the previous operation.

Users do not get these errors at the same time. And everything might be okay for a few hours / days and then the user gets one of the above errors. When they close MS Access and open it again everything works fine.

We checked the network to see if there was any network errors. Everything was fine with network.
We moved the mde file onto a new server but this did not resolve the problem.
I also checked the refernces and everything seems to be fine there as well.

I then moved the mde file on to one user's machine (locally) and everything is now fine for this user, while the other users (sharing the mde file) have continued to have problems.
So it looks like multiple users sharing the same mde file is what is causing the problem. And it seems to manifest itself if the user leaves the application idle for any length of time at all.

Has anyone encounted anything like this before? Is there any way around it without giving users their own local copy of the mde file?

Does Access have a limit on how many users can share an mde file? Is there any setting anywhere in Access that I can change for this?

I haven't changed the ODBC refresh interval or the OLE\DDE timeout settings in the Database advanced options. From what I understand about these they shouldn't be causing an issue. Is it worth setting these to extreme values?

Any ideas or suggestions would be appreciated.

Many Thanks
 
Last edited:
The db must be split. Each user gets a copy of the front end on thier hard drive and all front ends must be linked to the one back end [holding the tables]. Each user must have full permissions to the directory where the back end is located. 14 users is not too many for Access to handle. You might want to incorporate an idle timer to close the db if the user has left the db open for an hour and are not using it. Search around the forum for there are lots of threads related to all of the above. Good Luck!
 

Users who are viewing this thread

Back
Top Bottom