Any resolution for Err 3734 "Database has been placed..."

[Rey]

Howdy all.

Was wondering if there is any resolution for err 3734:
"The database has been placed in a state by user X on machine Y that
prevents it from being opened or locked."

I've spent time reearching err and found no real solution but then
maybe I stopped reading posts to soon 8-)

Believe this occurs after either an err has occurred and/or I've
stopped a process from completing. Is there some way of clearing any
left over locks or is this a case of page locking?
I have to exit Access and then reenter - sometimes I reboot 8-(

Thank you,
Rey

[Br]

Rey <re********@cox.net> wrote:

Howdy all.

Was wondering if there is any resolution for err 3734:
"The database has been placed in a state by user X on machine Y that
prevents it from being opened or locked."

I've spent time reearching err and found no real solution but then
maybe I stopped reading posts to soon 8-)

Believe this occurs after either an err has occurred and/or I've
stopped a process from completing. Is there some way of clearing any
left over locks or is this a case of page locking?
I have to exit Access and then reenter - sometimes I reboot 8-(

Thank you,
Rey

Depends I think on what you are doing...

If an error has occured in code then you should be doing some cleanup on
your error trapping code or something.... (eg. releasing
recordset/database objects manually).
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

[David W. Fenton]

"Rey" <re********@cox.net> wrote in
news:11**********************@g14g2000cwa.googlegr oups.com:

Was wondering if there is any resolution for err 3734:
"The database has been placed in a state by user X on machine Y
that
prevents it from being opened or locked."

I've spent time reearching err and found no real solution but then
maybe I stopped reading posts to soon 8-)

Believe this occurs after either an err has occurred and/or I've
stopped a process from completing. Is there some way of clearing
any left over locks or is this a case of page locking?
I have to exit Access and then reenter - sometimes I reboot 8-(

I assume you've tried deleting the LDB file and that fails because
it's in use?

And that you've used whatever functions the version of Windows uses
for managing open files?

This is not the kind of thing that should be happening often.
Indeed, it shouldn't happen at all. I think you'd be better off
trying to figure out *why* this happens, and fix *that*, rather than
spending time trying to solve it once the problem occurs.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Gord]

I have seen that error when multiple users share an .mdb file and one
of the users clicks the "Save" button on the toolbar while a form is
open. Sometimes people who start using Access after having used Word
and Excel think that they have to click the "Save" button after they
make changes to data in Access. They don't realize that the toolbar
button saves the _design_ of the form, not the data _in_ the form.
That's one of the reasons why I prefer to deploy front-ends as .mde
files wherever possible.

[David W. Fenton]

"Gord" <gd*@kingston.net> wrote in
news:11**********************@g43g2000cwa.googlegr oups.com:

I have seen that error when multiple users share an .mdb file and
one of the users clicks the "Save" button on the toolbar while a
form is open. Sometimes people who start using Access after having
used Word and Excel think that they have to click the "Save"
button after they make changes to data in Access. They don't
realize that the toolbar button saves the _design_ of the form,
not the data _in_ the form. That's one of the reasons why I prefer
to deploy front-ends as .mde files wherever possible.

Er, who in the world but someone who is a novice who doesn't know
better would have multiple users sharing a front end?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Gord]

>who in the world but someone who is a novice who doesn't know

better would have multiple users sharing a front end?

[1] Local IT staff who don't "officially support" Access applications.

[2] End-users who are left to fend for themselves and are not able to
contact me because I cost "real money".

Yes, both examples fit your definition of people who "don't know
better"....