I'm hoping somebody can shed some light on this problem...

We have a VB6 app that creates a text file in its working directory (this is the directory in which it's installed). It then copies this file to a networked computer by buffering it in using GET and buffering it out to the destination computer using PUT. The code creates handles to the files, transfers the data, then closes the handles. The handles do not create exclusive locks on the files.

What we are sometimes seeing is that the (destination?) OS/Filesystem is not closing the handle to the file. After the VB app has finished, the file is on the destination computer. If I try to delete the file through Explorer, Windows tells me the file is in use. If I disconnect the VB6 computer, Explorer still says the file is "in use".

The VB6 computer is W2KPro, the destination computer is W2KAdvServer. It's a Windows network.

Does anybody know of a problem with Windows, file I/O, and file handles?

Thanks for the help
Brian