Hi all,

I would appreciate any help on this matter. I have created an ADO connection to a .DBF visual FoxPro DB in my MDI app in VB6. I can access data from this DB and update any data successfully.

However, I need to run another app within my MDI app that needs to access this .DBF DB. So, before launching this app, I make sure that the ADO connection is closed and I also set the connection object to "Nothing". According to VB help, this is sufficient to release the hold on the DB file. Unfortunately, the other app still reports that the file is in used, so it cannot gain access to it. To make it short, the other app is doing a backup of that DB, and it needs to get hold of the .DBF file.

Do you have any thoughts on why this happens? I would appreciate any help on how to resolve this. I'm nearing the end of the project, and need to resolve this issue soon.

Thank you very much for all your help.

Khoi.

PS: Below is my code to close the connection:


    tblSetupDBF.Close

    setupDBFConn.Close

    'Really free up the connection
    Set setupDBFConn = Nothing

It shouldn't be very complicated at all, at least that's what I thought.

Khoi Nguyen

__________________
Khoi Nguyen

Hi there.. to a connection be close, it need to every recordset that it has open be close.. maybe you still has something opened around there that prevent the connection to be closed???

HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from dparsons signature and he Took that from planoie's profile
================================================== =========
My programs achieved a new certification (can you say the same?):
WORKS ON MY MACHINE
http://www.codinghorror.com/blog/archives/000818.html
================================================== =========
I know that CVS was evil, and now i got the proof:
http://worsethanfailure.com/Articles...-Hate-You.aspx
================================================== =========

Thanks for the reply.... I don't think that's an issue, since I only have one recordset for that connection, and I already called Close() on it, before I closed the connection object.

Khoi Nguyen