I have a MS-Access application which is used to access data stored on a SQL server. There are several people in the office that run the application.
It is most convenient (for keeping everyone running the latest version of the application) to keep a single copy of the compiled application (.ade file) in a central location so everyone can just open that file.
The problem is that after one person opens that file and is running the application, the next person gets a message saying that the application will be opened in 'Read Only Mode' because the file is locked for editing by another user. This leads people to believe that the SQL DATABASE is read-only which is not true. They can go ahead and run the application and edit data. They just can't go into form edit mode, etc. in Access.
Is there a way to eliminate that message about the Access Project being opened in read-only mode? I know if everyone has their own copy of the compiled project they wouldn't get the message, but then I would have to make sure everyone got a copy of the latest version.
It is most convenient (for keeping everyone running the latest version of the application) to keep a single copy of the compiled application (.ade file) in a central location so everyone can just open that file.
The problem is that after one person opens that file and is running the application, the next person gets a message saying that the application will be opened in 'Read Only Mode' because the file is locked for editing by another user. This leads people to believe that the SQL DATABASE is read-only which is not true. They can go ahead and run the application and edit data. They just can't go into form edit mode, etc. in Access.
Is there a way to eliminate that message about the Access Project being opened in read-only mode? I know if everyone has their own copy of the compiled project they wouldn't get the message, but then I would have to make sure everyone got a copy of the latest version.