Thanks for your reply! As you know I am not a low level programmer, only a RB user... So then is there some that know if the "nil" doing the same thing that close should do? Is the flag on the file changed to "not locked or not in use" ?
Here it is, not verified yet.. http://www.realsoftware.com/feedback/viewreport.php?reportid=kluojbyk Regards, Sven E On 2007-05-03, at 20:05, Norman Palardy wrote: > > On 03 May 2007, at 12:01, Sven E Olsson wrote: > >> >> if I have a code like this: >> >> f = GetFolderitem("myfile.txt") >> WriteToFile = f.CreateAsTextFile <<<<---------------- is the file >> locked now for other apps (in use by my self)? >> >> if WriteToFile <> nil then >> WriteToFile.WriteLine("Hello") >> WriteToFile.close <<<<---------------------- is the file unlocked now >> (not in use by my self) ? >> end if >> >> >> I ask, because it looks that the file is not closed properly (still >> in use by my self) and my app have to be closed and started agai, >> before I could do a new Save (write over the file) > > I believe Charles posted that there is a bug that CLOSE doe not do it > > Something like > > WriteToFile.close > WriteToFile = nil > > should if I recall correctly > _______________________________________________ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
