Altium Leaving Access Connection Open - Bug

If Altium is connected to an Access Database using a DBLib connection, when Altium is closed, Altium exits without closing the connection to the Access database.

Example:

Note this bug also applies to Access 2007 and higher *.accdb databases.

Shown below an Access Database that is closed. This is an Access back-end database 'Parts_ORW.MDB' that will be connected to Altium using *.DBLib.

Next Altium is launched and connected to 'Parts_ORW.MDB' through ORW.DBLib.

After installing 'ORW.DBLib' using your file browser, you can see a 'Parts_ORW.ldb'. This is a database lock file, which is created by Access when the database was opened and connected to by Altium.

Next close Altium without un-installing the *.DBLib Library.

Using your file browser again, you can see 'Parts_ORW.ldb'. The database lock file, which was created by Altium when the DBLib was installed is still visible. The database connection was left hanging open by Altium.

Altium should close any connections made to Access databases when.

Altium is Closed.
When the DBLib Library is un-installed.
When the DBLib Library is De-activated.

You can cleanup after Altium by opening the database and closing it after Altium has been closed.

Related links:

Microsoft CloseConnection Method for Access

"The CloseConnection method is useful when you have opened a Microsoft Access database from another application through Automation" i.e. like Altium :)

Altium Bug Crunch #3761

That's It . . .