"TonyG" <TonyG@junk.com> wrote in message
news:kZ%2j.65942$RX.31295@newssvr11.news.prodigy.net...
My program writes data to a file. I use CFileDialog to select the output
path and name. I have noticed something odd. If, using CFileDialog, I
select an output path and name that is located on my USB memory stick,
the file is written correctly. Naturally the CFileDialog has closed.
However when I click the tray icon to release the memory stick, the
operating system gives me a message saying that it can't release the
memory stick, try again later. It's the same message that I would get if
there was an explorer window open for a directory on the memory stick.
If I terminate my program, then I can release the memory stick, no
problem. BUT I don't want to have to terminate my program to be able to
release my memory stick.
Why is this happening? Can I prevent this problem?
By default CFileDialog changes your app's current directory to the one
that you navigated to in the dialog (on the USB stick). Since that is now
the app's current directory, it is busy, therefore you can't eject the USB
stick.
You can either do a SetCurrentDirectory() after you close the CFileDialog
to set the current directory to something else, or you can specify the
flag in CFileDialog that tells it not to set the current directory (don't
know what it is called offhand).