I have an MDB file set to "Compact on Close".

However, I will no longer be using Access to view and edit the MDB file. Instead I will be using a C-sharp application.

Will the DB continue to compact on close, that is, will it compact when the C-sharp application closes the connection?

Good question. I would not know.

However, one way to test is to deliberately create bloat that can be sizable.

You would create the bloat via the application (well, actually a prototype) then see if it get compacted once you close it away.

One way to create bloat is execute ad hoc query using dynamic SQL several times again and again while looping through a recordset

I have an MDB file set to "Compact on Close".

However, I will no longer be using Access to view and edit the MDB file. Instead I will be using a C-sharp application.

Will the DB continue to compact on close, that is, will it compact when the C-sharp application closes the connection?

I have not ever had a back end compact when a front end exits if the back end is set to compact on close. AFAIK, the compact on close is only used when the actual Access application (MSACESS.exe) opens the database directly.

I personally do not ever use it. I prefer to always back up an database before it is compacted. I want to be able to control the compact action. I also do not ever compact an database across the network.

Thanks guys. That's the info I needed.

You're welcome!

Glad we could assist.