Presumably you're seeing 102 because the file is open for writing.
My experience is that FolderItem objects are unreliable for anything
that changes during the existence of an object; I frequently end up
resorting to system calls to get things to work.
Charles Yeomans
On Aug 12, 2006, at 4:56 PM, Dennis Birch wrote:
I am testing after writing, with no success. Even after fixing the
file writing problem by setting the BinaryStream.Position to 0 before
writing, I'm still seeing a LastErrorCode of 102 when I inspect the
FolderItem's properties in the debugger, but the variable I then stuff
it into always has a value of 0.
On 8/12/06, Charles Yeomans <[EMAIL PROTECTED]> wrote:
I think you'll have better result checking bs.LastErrorCode for write
errors. I'm not sure why you're seeing inconsistent results with
FolderItem.LastErrorCode.
_______________________________________________
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>
