Access VBA application: Placed in a State that prevents it from being opened or locked
I am developing an Access 2013 application. In testing, the first time I run through my process, it works. When I try to run the application a second time, I get the message, "The database has been placed in a state...that prevents it from being opened or locked."
I am developing this on my laptop. There is no network, or multiple users involved. The application retrieves data from a SQL Server database and copies it into an Access table. The error shown in the attached image occurs at this statement: cnDest.Open CurrentProject.Connection
Dim cnDest As New ADODB.Connection
cnDest.Open CurrentProject.Connection
If I close access and open it up again, the error is gone and I can run the process again...but that is not a fix for the problem. I researched on the web...nothing conclusive.
Thanks for your help
PlacedInAStateError.JPG
I am developing this on my laptop. There is no network, or multiple users involved. The application retrieves data from a SQL Server database and copies it into an Access table. The error shown in the attached image occurs at this statement: cnDest.Open CurrentProject.Connection
Dim cnDest As New ADODB.Connection
cnDest.Open CurrentProject.Connection
If I close access and open it up again, the error is gone and I can run the process again...but that is not a fix for the problem. I researched on the web...nothing conclusive.
Thanks for your help
PlacedInAStateError.JPG
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Yes, I close it...the end of my procedure has
SourceRs.Close
Set SourceRs = Nothing
cnDest.Close
Set cnDest = Nothing
I will try to redo things without even using cnDest
SourceRs.Close
Set SourceRs = Nothing
cnDest.Close
Set cnDest = Nothing
I will try to redo things without even using cnDest
Keep in mind that the point of using CurrentProject.Connection is that you get to use Access's own ADO connection object, so you don't need to do your own.
If you want your own because you want to change the connection properties, then you'd specify the provider and all the properties, not use Access's connection.
Jim.
If you want your own because you want to change the connection properties, then you'd specify the provider and all the properties, not use Access's connection.
Jim.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial