I'm trying to tune my File..Save process and running into a frustrating problem on Windows.
When overwriting a binary file, I first save a copy for save keeping (in temp location). Then I open the original file, set it's size to 0 and start writing. Now it's true that I have just had the original file open in order to read it in as a document but I am pretty certain that I have properly closed the bStream prior to this exercise. I even went through the stack looking for lost 'binaryStream' objects and couldn't find any. So, on the Mac, no problem. On Windows (XP SP2 in this case) I can't open the file for binary output as it comes up as 'busy'. This happens in RB 2006 and 2007. The fact that it works fine on the Mac hints that it may be an RB bug on Windows not giving up the file from the previous read. Has anyone seen this issue? It's in the process of driving me nuts... thanks. Regards, Steve Upton -- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
