Using ADOX with C#.

[Frank Rizzo]

I am using ADOX to make changes to an Access database that would be
difficult to do via the System.Data.OLE DBClient. So far I have no
trouble actually doing the work, however, I have trouble closing the
connection to the Access database.

//open connection
ADOX.CatalogCla ss connection = new ADOX.CatalogCla ss();
connection.let_ ActiveConnectio n(this.Connecti onString);

//do the work
....

//close the connection
((ADODB.Connect ion) connection.Acti veConnection).C lose();
Marshal.Release ComObject(conne ction);

Even though the code to close the connection does cause an error, it
doesn't actually close the connection, because if I try to connect to
the database later, it errors out saying that it is exclusively locked.

How do I actually close the connection created via ADOX?

Thanks

[Nicholas Paldino [.NET/C# MVP]]

Frank,

Just off the top of my head, do you have connection pooling turned on?
Perhaps this has something to do with it.

Also, did you dispose of the catalog class properly?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Frank Rizzo" <no**@none.co m> wrote in message
news:e5******** *****@TK2MSFTNG P14.phx.gbl...

I am using ADOX to make changes to an Access database that would be
difficult to do via the System.Data.OLE DBClient. So far I have no trouble
actually doing the work, however, I have trouble closing the connection to
the Access database.

//open connection
ADOX.CatalogCla ss connection = new ADOX.CatalogCla ss();
connection.let_ ActiveConnectio n(this.Connecti onString);

//do the work
...

//close the connection
((ADODB.Connect ion) connection.Acti veConnection).C lose();
Marshal.Release ComObject(conne ction);

Even though the code to close the connection does cause an error, it
doesn't actually close the connection, because if I try to connect to the
database later, it errors out saying that it is exclusively locked.

How do I actually close the connection created via ADOX?

Thanks

[Frank Rizzo]

Nicholas Paldino [.NET/C# MVP] wrote:

Frank,

Just off the top of my head, do you have connection pooling turned on?
Perhaps this has something to do with it.

Also, did you dispose of the catalog class properly?
Well, I guess that's the crux of the matter. How does one dispose of it
properly?

I thought

Marshal.Release ComObject(conne ction);

will do the trick.

[Nicholas Paldino [.NET/C# MVP]]

Frank,

Yes, you are releasing the connection, but that is not the only COM
object there is. There is also the catalog object.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Frank Rizzo" <no**@none.co m> wrote in message
news:u6******** ******@TK2MSFTN GP09.phx.gbl...

Nicholas Paldino [.NET/C# MVP] wrote:

Frank,

Just off the top of my head, do you have connection pooling turned
on? Perhaps this has something to do with it.

Also, did you dispose of the catalog class properly?

Well, I guess that's the crux of the matter. How does one dispose of it
properly?

I thought

Marshal.Release ComObject(conne ction);

will do the trick.

[Frank Rizzo]

Nicholas Paldino [.NET/C# MVP] wrote:

Frank,

Yes, you are releasing the connection, but that is not the only COM
object there is. There is also the catalog object.

Connection is the catalog object. Consider the code:

//open connection
ADOX.CatalogCla ss connection = new ADOX.CatalogCla ss();
connection.let_ ActiveConnectio n(this.Connecti onString);

//do the work
....

//close the connection
((ADODB.Connect ion) connection.Acti veConnection).C lose();
Marshal.Release ComObject(conne ction);