By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,285 Members | 1,659 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,285 IT Pros & Developers. It's quick & easy.

Error drving me insane

P: n/a
Hello,

I am using Access 2003 to develop a database, and keep getting this
error Run-time error '-2147467259 (80004005)

The database has been placed in a state by user 'Admin' on machine
'XXXXX' that prevents it from being opened or locked.

When I first open the database I do not get this error, I only seem to
get this after doing step through code.

I then have to close the database and reopen it where I can run the
program until I enter the code editor again.

Any ideas how I can fix this, a search in ms help returns nothing

Thanks
Oct 11 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hello!

"Yerit" <Ye***@noaddress.org:
I am using Access 2003 to develop a database, and keep getting this error
Run-time error '-2147467259 (80004005)

The database has been placed in a state by user 'Admin' on machine 'XXXXX'
that prevents it from being opened or locked.

Any ideas how I can fix this, a search in ms help returns nothing

Hmm... I usually get this error if I try to import or export from a database
where a form or report is opened in design mode. Maybe that's the same
reason as for your message?

Regards

MaiThai
Oct 11 '06 #2

P: n/a
Yerit wrote:
Hello,

I am using Access 2003 to develop a database, and keep getting this
error Run-time error '-2147467259 (80004005)

The database has been placed in a state by user 'Admin' on machine
'XXXXX' that prevents it from being opened or locked.

When I first open the database I do not get this error, I only seem to
get this after doing step through code.

I then have to close the database and reopen it where I can run the
program until I enter the code editor again.

Any ideas how I can fix this, a search in ms help returns nothing

Thanks
Go to http://groups.google.com/advanced_search?hl=en
In the Groups box enter
*Access*
In the SearchForText box enter
The database has been placed in a state

Lots of hits. You may find something in one of them that assists you.
Oct 11 '06 #3

P: n/a
Go to http://groups.google.com/advanced_search?hl=en
In the Groups box enter
*Access*
In the SearchForText box enter
The database has been placed in a state

Lots of hits. You may find something in one of them that assists you.
Hi thanks for this, the problem seems to be that editing forms or
modules somehow places the DB in an exclusive state.

I have all service pack installed for office 2003, and have tried the
repair method.

The problem goes away when I close the DB an re open until the next time
I edit code or a form.

This is most annoying, and have concluded that I am no longer able to
work like this, lest I end up throwing the computer out of the window or
worse (better?) myself!!

I have now decided to write this on SQL Server 2000 using C#

Thanks for all you help it is appreciated, but I do not have any more
time to spare trying to figure this problem out.

Yerit
Oct 11 '06 #4

P: n/a
Yerit wrote:
>Go to http://groups.google.com/advanced_search?hl=en
In the Groups box enter
*Access*
In the SearchForText box enter
The database has been placed in a state

Lots of hits. You may find something in one of them that assists you.


Hi thanks for this, the problem seems to be that editing forms or
modules somehow places the DB in an exclusive state.

I have all service pack installed for office 2003, and have tried the
repair method.

The problem goes away when I close the DB an re open until the next time
I edit code or a form.

This is most annoying, and have concluded that I am no longer able to
work like this, lest I end up throwing the computer out of the window or
worse (better?) myself!!

I have now decided to write this on SQL Server 2000 using C#

Thanks for all you help it is appreciated, but I do not have any more
time to spare trying to figure this problem out.

Yerit
Have you /decompile the mdb?

Then recompile the code?
Oct 11 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.