Error when using a shared database - cannot open/lock

[Kylie]

I see that there are some other users who have had a similar problem to mine,
but was unable to find a solution to the problem, so here goes:

The following error message is appearing when users attempt to open either
the front end or the back end of a split database used by 7 users (currently
with 2 users using the front-end throughout the day, and one using the
back-end throughout the day):

The database has been placed in a state by user [user name] on machine
[computer name] that prevents it from being opened or locked.

We have been using the database without problems over the past few months
with all users bar one only using the front end on their machines. However,
a new employee has just begun and is predominantly working in the back-end of
the database, open throughout the day. I have ensure that 'Shared' is the
option under the Advanced tab in the Options menue, so this is not the
problem. Would the problem be because she is using the back-end for long
periods at a time? When the new user shuts down Access, others can then open
it; however it is not always practicle to have to keep asking her to close
the database. (Or is this an Access flaw??)

This database is crucial to a project we are working on with an end of
December deadline, so I would really appreciate your help! (Beginner Access
user here!)

Thanks,
Kylie

 

[Tom Wickerath]

Hi Kylie,

Why is your new user opening the back-end directly? There should be no
legitimate need for this. A couple of possibilites:

1.) Your new user does not have full privileges (RWCD) for the shared
folder. Therefore, a locking database file cannot be created when this user
opens the database. Without a locking database file, the database is opened
in exclusive mode. Try a simple test from this user's PC (logged in as this
user):

Use Notepad to create a text file. Add any text to this file. Save it to the
shared folder. Are you able to do this? Close the file and then re-open it.
Are you able to edit the text and save it? Then use Windows Explorer to
delete the file. Are you able to delete it? Please see the following KB
article:

Introduction to .ldb Files
http://support.microsoft.com/?id=299373


2.) The second possibility is that your new user is opening an object in
design view. This promotes her lock to exclusive access. The lock, once
promoted, does not automatically revert back to shared access when the user
closes the object. This would require that the person completely exit the
database first.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________


:

I see that there are some other users who have had a similar problem to mine,
but was unable to find a solution to the problem, so here goes:

The following error message is appearing when users attempt to open either
the front end or the back end of a split database used by 7 users (currently
with 2 users using the front-end throughout the day, and one using the
back-end throughout the day):

The database has been placed in a state by user [user name] on machine
[computer name] that prevents it from being opened or locked.

We have been using the database without problems over the past few months
with all users bar one only using the front end on their machines. However,
a new employee has just begun and is predominantly working in the back-end of
the database, open throughout the day. I have ensure that 'Shared' is the
option under the Advanced tab in the Options menue, so this is not the
problem. Would the problem be because she is using the back-end for long
periods at a time? When the new user shuts down Access, others can then open
it; however it is not always practicle to have to keep asking her to close
the database. (Or is this an Access flaw??)

This database is crucial to a project we are working on with an end of
December deadline, so I would really appreciate your help! (Beginner Access
user here!)

Thanks,
Kylie

 

[dbahooker]

MDB is crap use ADP.. if you care enough about your data to keep it in
a database; put it in a reliable database-- MSDE or SQL Server are a
lot more reliable; and a lot higher-performance than MDB.. i mean.. the
indexing is wonderful in SQL Server.

 

[Kylie]

Hi Tom

Thank you for your reply (and all your help in the past - all has been going
really well until this point!)

I will look into your suggestions, but you may also be able to clarify this
related issue for me: The user is using the back-end directly because she is
compiling a large number of queries which we want to save. This is where I
get a little confused - if she does the queries on the front-end, when I
distribute a new copy of the front-end the previous queries will be removed,
ie: when I remove the old front-end and replace with the new one. I know
that there must be a way around this, and if there is, that would solve the
initial problem I suppose! Help appreciated as always!

Thanks, Kylie

Hi Kylie,

Why is your new user opening the back-end directly? There should be no
legitimate need for this. A couple of possibilites:

1.) Your new user does not have full privileges (RWCD) for the shared
folder. Therefore, a locking database file cannot be created when this user
opens the database. Without a locking database file, the database is opened
in exclusive mode. Try a simple test from this user's PC (logged in as this
user):

Use Notepad to create a text file. Add any text to this file. Save it to the
shared folder. Are you able to do this? Close the file and then re-open it.
Are you able to edit the text and save it? Then use Windows Explorer to
delete the file. Are you able to delete it? Please see the following KB
article:

Introduction to .ldb Files
http://support.microsoft.com/?id=299373


2.) The second possibility is that your new user is opening an object in
design view. This promotes her lock to exclusive access. The lock, once
promoted, does not automatically revert back to shared access when the user
closes the object. This would require that the person completely exit the
database first.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________


:

I see that there are some other users who have had a similar problem to mine,
but was unable to find a solution to the problem, so here goes:

The following error message is appearing when users attempt to open either
the front end or the back end of a split database used by 7 users (currently
with 2 users using the front-end throughout the day, and one using the
back-end throughout the day):

The database has been placed in a state by user [user name] on machine
[computer name] that prevents it from being opened or locked.

We have been using the database without problems over the past few months
with all users bar one only using the front end on their machines. However,
a new employee has just begun and is predominantly working in the back-end of
the database, open throughout the day. I have ensure that 'Shared' is the
option under the Advanced tab in the Options menue, so this is not the
problem. Would the problem be because she is using the back-end for long
periods at a time? When the new user shuts down Access, others can then open
it; however it is not always practicle to have to keep asking her to close
the database. (Or is this an Access flaw??)

This database is crucial to a project we are working on with an end of
December deadline, so I would really appreciate your help! (Beginner Access
user here!)

Thanks,
Kylie

 

[Tom Wickerath]

Hi Kylie,

Your user could save a copy of the front-end with a different name. Then,
when you distribute a new front-end, she can import all of her queries into
the new front-end .mdb file.

A more elegant solution involves writing VBA code to produce what is
commonly called Query by Form (QBF). I am not talking about the same QBF that
is built into Access. In the method that I'm talking about, one uses VBA code
to create the WHERE portion of a SQL statement (or the entire SQL statement
if they really want to). This type of functionality can usually reduce the
need for a lot of individual saved queries.

I think (?) I may have sent you a copy of a QBF demo in the past by private
e-mail. If this doesn't sound familiar, then let me know and I will send you
a copy. This sample demonstrates the power of QBF.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Hi Tom

Thank you for your reply (and all your help in the past - all has been going
really well until this point!)

I will look into your suggestions, but you may also be able to clarify this
related issue for me: The user is using the back-end directly because she is
compiling a large number of queries which we want to save. This is where I
get a little confused - if she does the queries on the front-end, when I
distribute a new copy of the front-end the previous queries will be removed,
ie: when I remove the old front-end and replace with the new one. I know
that there must be a way around this, and if there is, that would solve the
initial problem I suppose! Help appreciated as always!

Thanks, Kylie
__________________________________________

:

Hi Kylie,

Why is your new user opening the back-end directly? There should be no
legitimate need for this. A couple of possibilites:

1.) Your new user does not have full privileges (RWCD) for the shared
folder. Therefore, a locking database file cannot be created when this user
opens the database. Without a locking database file, the database is opened
in exclusive mode. Try a simple test from this user's PC (logged in as this
user):

Use Notepad to create a text file. Add any text to this file. Save it to the
shared folder. Are you able to do this? Close the file and then re-open it.
Are you able to edit the text and save it? Then use Windows Explorer to
delete the file. Are you able to delete it? Please see the following KB
article:

Introduction to .ldb Files
http://support.microsoft.com/?id=299373


2.) The second possibility is that your new user is opening an object in
design view. This promotes her lock to exclusive access. The lock, once
promoted, does not automatically revert back to shared access when the user
closes the object. This would require that the person completely exit the
database first.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I see that there are some other users who have had a similar problem to mine,
but was unable to find a solution to the problem, so here goes:

The following error message is appearing when users attempt to open either
the front end or the back end of a split database used by 7 users (currently
with 2 users using the front-end throughout the day, and one using the
back-end throughout the day):

The database has been placed in a state by user [user name] on machine
[computer name] that prevents it from being opened or locked.

We have been using the database without problems over the past few months
with all users bar one only using the front end on their machines. However,
a new employee has just begun and is predominantly working in the back-end of
the database, open throughout the day. I have ensure that 'Shared' is the
option under the Advanced tab in the Options menue, so this is not the
problem. Would the problem be because she is using the back-end for long
periods at a time? When the new user shuts down Access, others can then open
it; however it is not always practicle to have to keep asking her to close
the database. (Or is this an Access flaw??)

This database is crucial to a project we are working on with an end of
December deadline, so I would really appreciate your help! (Beginner Access
user here!)

Thanks,
Kylie

 

[dbahooker]

mdb is crap. use msde or sql server.

Access Data Projects make much better queries than this mdb crap