101 error when deleting a file

[Harrie Westphal <harriew at frontiernet dot net>]

Is there a logical reason why REALbasic sets FolderItem.LastErrorCode  
to 101 when you delete a file? Watching the events in the debugger  
you can see that the file exists, has been read in and it shows the  
f.exists=true, f.LastErrorCode=0. Now when f.delete is executed  
f.exists goes to false, which I would expect, but f.LastErrorCode  
goes to 101, which seems odd. Yes, the file no longer exists which is  
what 101 is telling you, but it existed at the point in time when the  
f.delete was executed so why throw a 101 error at that time? I guess  
you could argue that that is verification that the file was deleted,  
but f.exists going to false would also tell you that. Just seems odd  
to me.


=== A Mac addict in Tennessee ===

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>