On Jan 31, 2006, at 5:52 PM, Adam Ernst wrote:
On Jan 31, 2006, at 7:49 PM, Norman Palardy wrote:
if oldFile.Exists then f.CreationDate = oldFile.CreationDate
// oldFile probably exists. But I don't want to delete it
first--that would sacrifice safety.
if oldfile.exists then oldFile.delete
f.MoveFileTo oldFile
if f.LastErrorCode <> 0 then return false // LastErrorCode=183,
"file already exists"
That deletes the oldFile. What if the move then fails (permissions
error, or something)?
You might try renaming the old file, but that may fail for privilege
reasons as well.
Move is just a MOVE, not a MOVE AND REPLACE
On Mac, it's a move and replace (I think).
It can be.
The Mac, because of the Unix underpinnings will let you replace a file
that is open (including an executable).
In fact try deleting a file you are writing to.
The finder may not let you, but in Terminal if you do "rm" on a file
being written to it will delete BUT the unix system hangs on to it
until you free it up (and this can be a nasty source of disappearing
disk space :))
Some versions of Windows will. Some will not
However, if oldFile is "busy" you may not be able to remove it,
rename it or anything else
Yes. That's fine. I just want to replace it if it's not busy.
Then you get an error if it is.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|