cipriano555
asked on
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
are you closing the cnDest after using it?
cnDest.close
cnDest.close
ASKER
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I got rid of cnDest and just used CurrentProject.Connection directly, problem solved.
Jim.