Recordset is disconnected, but a connection to MS Access MDB still persists

I am trying to create a disconnected recordset against an MS Access database.  I have set all the properties as instructed via documentation and other posts, yet the .LDB file persists - indication an active connection to the database.  How can I have a truly disconnected recordset against an MS Access database.  I am not interested in copying a recordset by opening a recordset then sequentially copying the records to another recordset that I created from scatch - this is much too slow.  Here is some code I have tried:
  1.             Dim mrsGrid as New ADODB.Recordset
  2.            
  3.             myADOconnection.open
  4.              With mrsGrid
  5.                         .CursorLocation = adUseClient
  6.                         .CursorType = adOpenForwardOnly
  7.                        .Open strSQL, myADOconnection, adOpenStatic, adLockBatchOptimistic
  8.                       .MoveLast
  9.              End With
  10.            Set mrsGrid.ActiveConnection = Nothing
  11.            myADOconnection.Close
  12.            mrsGrid.Close

Yet, even though the connection is closed the .ldb file still is there?  Things to note:
1. before I run this code there is no connection to the mdb file (no ldb file exists).
2.  Upon stepping past line 3 a ldb file is created (as expected)
3.  Upon stepping past line 11, ldb file still exists - yet connection is close (and reports being closed properly - i.e., if I check at this point with a break and in the command window, I get adStateClosed for myADOconnection).  
4.  Not until I execute line 12 does the ldb close and go away?
So, how can I REALLY have a disconnected recordset.  You may be asking why is this necessary?  Because Access databases corrupt any chance they get and this is very bad for customers.