BoulderRidge
Programmer
I have an application developed in Access 2007/Windows ME and running on Access 2010/Windows 7. The Back End shared database lives on a network server. Version 1 deployed a year ago and suffered from periodic corruption. I finally discovered that it had not been deployed as intended and multiple users were running the same physical copy of the Front End app from the network. I believe this caused the corruption.
To resolve this we changed the deployment strategy last month. Now the Front End application is deployed as follows:
a. Each user has a separate subfolder on the network containing a separate physical copy of the FE app in accde format.
b. For each copy of the FE app there is a separate shortcut which is copied to that user’s computer to launch the app.
c. So User A has a shortcut on their local desktop that points to the accde FE app file in the User A subfolder on the network.
d. Every user’s copy of the FE app is linked to the same shared BE database.
This configuration has been working successfully for about one month.
Last week I released an upgraded version of the application with additional features. Ever since I have gotten reports of the following error: -2147217887 Could not update; currently locked by user “Admin” on machine “xxxxx.”
Most posts re this error talk about either a memo field or page level locking. I have no memo fields. I have everything set to Record Level locking—does that equate to locking a whole page anytime one user does an edit? If so that would be a problem since even though each user has their own subset of records to edit (recording survey results) all of the active records subject to these edits would be adjacent to each other. But why would the error just start showing up now?
The most recent report of this same error occurred when the last user who was logged in exited the application. It doesn’t seem possible that any other user could have a page locked in this scenario.
In case it may be relevant, we have always had ongoing connectivity issues because the users are working on wireless tablets and moving around in the building. Sometimes they step out of range and lose their connection; when this happens they Exit the application and relaunch it is seems to resolve the problem.
I can post more details or answer specific questions if anyone wants to dig in. Thanks!
-- BoulderRidge B-)
To resolve this we changed the deployment strategy last month. Now the Front End application is deployed as follows:
a. Each user has a separate subfolder on the network containing a separate physical copy of the FE app in accde format.
b. For each copy of the FE app there is a separate shortcut which is copied to that user’s computer to launch the app.
c. So User A has a shortcut on their local desktop that points to the accde FE app file in the User A subfolder on the network.
d. Every user’s copy of the FE app is linked to the same shared BE database.
This configuration has been working successfully for about one month.
Last week I released an upgraded version of the application with additional features. Ever since I have gotten reports of the following error: -2147217887 Could not update; currently locked by user “Admin” on machine “xxxxx.”
Most posts re this error talk about either a memo field or page level locking. I have no memo fields. I have everything set to Record Level locking—does that equate to locking a whole page anytime one user does an edit? If so that would be a problem since even though each user has their own subset of records to edit (recording survey results) all of the active records subject to these edits would be adjacent to each other. But why would the error just start showing up now?
The most recent report of this same error occurred when the last user who was logged in exited the application. It doesn’t seem possible that any other user could have a page locked in this scenario.
In case it may be relevant, we have always had ongoing connectivity issues because the users are working on wireless tablets and moving around in the building. Sometimes they step out of range and lose their connection; when this happens they Exit the application and relaunch it is seems to resolve the problem.
I can post more details or answer specific questions if anyone wants to dig in. Thanks!
-- BoulderRidge B-)
