C
ccool
Our company is in the process of converting Access 97 DB's to Access 2003.
However, a recurring problem has crept up that must be addressed.
In a newly converted database when a user opens it and enters data into a
form or is in design view all other users are denied access to the database
and the following error appears:
The database has been placed in a state by user 'Admin' on machine 'blah'
that prevents it from being opened or locked.
I have goggled and found solutions suggesting the database be split into a
front end and a back end and each user have a copy of the front end placed on
their personal drive. Although this solution would probably work it is not a
viable solution for our company due to the shear number of databases on the
network and the number of employees involved and the amount of changes being
made to the databases.
Although this issue did not occur with access 97 databases. We have been
able to duplicate the issue with a database that has been developed in Access
2003 not converted suggesting the issue is not with the conversion but with
Access 2003.
Is there another fix to this problem? We would like to continue using the
newly converted databases as we were when they were in Access 97.
However, a recurring problem has crept up that must be addressed.
In a newly converted database when a user opens it and enters data into a
form or is in design view all other users are denied access to the database
and the following error appears:
The database has been placed in a state by user 'Admin' on machine 'blah'
that prevents it from being opened or locked.
I have goggled and found solutions suggesting the database be split into a
front end and a back end and each user have a copy of the front end placed on
their personal drive. Although this solution would probably work it is not a
viable solution for our company due to the shear number of databases on the
network and the number of employees involved and the amount of changes being
made to the databases.
Although this issue did not occur with access 97 databases. We have been
able to duplicate the issue with a database that has been developed in Access
2003 not converted suggesting the issue is not with the conversion but with
Access 2003.
Is there another fix to this problem? We would like to continue using the
newly converted databases as we were when they were in Access 97.