Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 215
  • Last Modified:

Problem deleting an access database

I am trying to close a database and delete the mdb file.  However, when I do this, it does not delete the file because the file is still locked.  I get a runtime error '70' Permission Denied.  Using DAO 3.6, is there a way to check to see if the mdb is still locked and wait until it is ok to delete it or is there a better way to do this?

If Not (Dbs Is Nothing) Then
   Dbs.Close
   Set Dbs = Nothing
   Data1.Database.Close
   Data2.Database.Close
   DoEvents
End If
sFileSpec = ProjectPath & "\" & ProjectName & ".mdb"
If Dir(sFileSpec) <> vbNullString Then Kill sFileSpec
0
joesmow
Asked:
joesmow
  • 9
  • 4
  • 3
  • +1
1 Solution
 
mdouganCommented:
The best way to check to see if the db is in use is to close it, then try to reopen it in Exclusive mode.  If this throws a run-time error, then the db is still in use.  If not, then you can close and delete it.

I know it sounds like a kludge, but this is what MS recommends.
0
 
Richie_SimonettiIT OperationsCommented:
Use Dir$ function to locate yourdbname.ldb file, if it is still there, someone is  using it.
Something like this:

if dir$("c:\dbpath\mydb.ldb",vbarchive)="" then
   kill "c:\dbpath\mydb.mdb"
end if
0
 
Richie_SimonettiIT OperationsCommented:
Seeing your code, maybe you are having time problems between close the db (data control releases de connection)  and try to kill it.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
joesmowAuthor Commented:
First, what properties do I use to open it in Exclusive mode?

Set dbs = dbEngine.OpenDatabase ("C:\data.mdb, ........)

Second, if I am openning it again, it seems like I will have the same problem when I close it again and try to delete it.

Richie,

Timing is the problem.  It tries to kill it before the file is completely released.  If I use a loop like the following then the file is never released:

While Dir("c:\mydb.ldb) <> ""
    DoEvents
Wend

Or

While Not Dbs Is Nothing
   DoEvents
Wend

Any other suggestions?

0
 
joesmowAuthor Commented:
First, what properties do I use to open it in Exclusive mode?

Set dbs = dbEngine.OpenDatabase ("C:\data.mdb, ........)

Second, if I am openning it again, it seems like I will have the same problem when I close it again and try to delete it.

Richie,

Timing is the problem.  It tries to kill it before the file is completely released.  If I use a loop like the following then the file is never released:

While Dir("c:\mydb.ldb) <> ""
    DoEvents
Wend

Or

While Not Dbs Is Nothing
   DoEvents
Wend

Any other suggestions?

0
 
joesmowAuthor Commented:
Increasing points to 1000.
0
 
joesmowAuthor Commented:
Sorry. It will not let me go above 500.
0
 
joesmowAuthor Commented:
Sorry. It will not let me go above 500.
0
 
joesmowAuthor Commented:
Sorry. It will not let me go above 500.
0
 
joesmowAuthor Commented:
Sorry. It will not let me go above 500.
0
 
mdouganCommented:
It's the third parameter in the OpenDatabase statement:

Set db = OpenDatabase("bob", adOpenDynaset, True)
0
 
mdouganCommented:
I'm sorry, I got that wrong.  It's the second parameter, the third parameter is read-only.  So, that would be:

Set db = OpenDatabase("bob", True, True)
0
 
DalinCommented:
First, what properties do I use to open it in Exclusive mode?

Set dbs = dbEngine.OpenDatabase ("C:\data.mdb,True)


When you get error 70, it mean some other program has opened the database.  So you don't realy need to check again. Just use error handling


On error goto handler



Exit sub
Handler:
Select case err.number

Case 70
   'Database open, do whatever you need to do to close
   Resume
Case else

End Select

End Sub

0
 
joesmowAuthor Commented:
It still doesn't work.  Even if I close the Exclusive database in the error handler, by the time it gets back to the kill statement, the database is still locked.
0
 
Richie_SimonettiIT OperationsCommented:
Do you have any recordset still open that avoid you to close db and connections properly?
0
 
joesmowAuthor Commented:
Bingo!  I went back through and found a recordset I forgot to close.  When I closed the recordset properly, it allowed me to delete the file.  Thanks everyone.
0
 
Richie_SimonettiIT OperationsCommented:
Glad to help.
Thanks for "A" grade.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 9
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now