run time error '3009'?

[irethedo]

I am getting a

=======================
run time error '3009'

You tried to lock table 'DataEntry qry' while trying to open it, but the table cannot be locked because it is iin current use. Wait a moment, and then try the operation again.
============

Has anyone seen this error before and what can I do to fix this? I have exited out of the database and when I get back into it, this message keeps popping up when I try to launch my form...

Please advise

Thank you

 

[HitechUser]

irethedo,

Is someone else in the database? Or do you have another form already opened?

When you close the database does the .LDB get deleted?

I had this problem once, no matter what I did I could not get rid of the error. So I created a new empty database (not a copy) and imported evrything back in and it all worked fine!

Let me know...

 

[irethedo]

Thanks HitechUser-

I reverted back to an older saved copy because I could not get rid of it but then it popped up again...

This time, what happened is that I updated a query from a select query to an update query which is the record source for a form and even though the form was not open, I got this error the next time that I tried to open the form.

And now I can't get rid of it...

i creaated aa new database as you suggested and copied each table, query, form, & report to it (I am assuming that is what you meant by importing everything into a new database)

and the problem still remains...

any other ideas of what I might try?

 

[Pampers]

Hi irethedo,
Pampers again. There is no need to use an update query, you need an have updatable select query. The error pops up because the update query runs (with an error) when the form is loaded. Change the query back the a select query.

Pampers
Just back from holiday...
that may it explain it.

 

[irethedo]

Thanks Pampers

It is still a Select Query, I never changed it....

I found the problem to be that the form properties was set to record locks and I set it to no record lock and it works fine now...

This should be a one user database but eventually it may be many users at which time I may have to rethink this strategy when that time comes...

 

[Pampers]

I believe the no record lock-option, is actually a so called optimistic locking scenario. The record will be locked as it is saved.

Pampers
Just back from holiday...
that may it explain it.