.ldb file stays when connection is closed

  • Thread starter Thread starter Derrick
  • Start date Start date
Ok, take tomorrow off too. Tell your boss I said it was OK!


Derrick said:
I feel like taking the day off now - finally it is fixed.

I had to modify your suggestion a bit (I had to cast the active connection
as a adodb.connection), but this worked.

Dim cat As Catalog = New Catalog
cat.Create(Me.CreateString)
CType(cat.ActiveConnection, ADODB.Connection).Close()

Thanks so much for your help.

Derrick
Click to expand...
 
Hi Derrick,

It was nice to know that you have had the problem fixed. Thanks for Paul
and Scott's responses. Thank you for sharing your experience with all the
people in the community. If you have any questions, please feel free to
post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
¤ Actually, I'm questioning whether the JET OLEDB Provider needs to support
¤ connection pooling since this is not the connection itself, only the
¤ instructions to the connection on what type of DB and where it is.
¤
¤ I was under the impression that connections to Access databases participate
¤ in connection pooling just as all others in ADO.NET do.
¤
¤ Are you sure you are not confusing connection pooling in ADO with ADO.NET?

I'm not making the distinction. The native OLE DB provider is simply an added (managed code) layer
to the data access mechanism. Ultimately it still has to interop with the COM based (non managed
code) OLE DB provider.

My understanding of how this works is that whether you are using the generic native ODBC or OLEDB
..NET managed code wrappers, connection pooling is still determined by the capability of the database
driver, which in this instance is COM OLEDB and Jet.

This certainly seems to be consistent with the fact that no connection pooling is evident when using
ADO.NET and the OLEDB provider.

In any event, even if ADO.NET and the native OLEDB provider library *did* support connection pooling
it would not have applied in this case since it was the ADOX code that was causing the issue.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top