Consider that JET/Access databases cache all IO to improve performance. This
means that when uploading bulk data, the engine does not actually write to
the file until it's in "idle" mode. Be sure to give your application enough
time to let JET finish the process. Of course, this is expected behavior
with this engine--it's why many choose more robust database engines.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

[quoted text, click to view]

Hi,

I am new at using the BackgroundWorker so please forgive me if this topic
has already been covered.

I'm using BackgroundWorker to import data into an Access 2000 database using
OleDbConnection. After the thread is complete, I'm noticing that the Access
..ldb lock file still remains, and does not disappear until I close all the
way out of my program. Since the call to Open the OleDbConnection is inside
of the thread (in the DoWork function) how can I force the OleDbConnection
to Close so I can rename my .mdb file?

TIA!!

--Eric