Fergus,
I've looked into the content of the file at each point where the exception
occurs, and there appears to be absolutely no correlation between the bytes.
I'm not sure if VB is trying to do any kind of underlying conversion, but I
certainly am not
Tim
"Fergus Cooney" <filter-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
Hi Tim,
I've got no idea what the problem is but I'm intrigued by 'Furthermore,
the number of bytes read before the error occurs is always the same,
assuming
I am using the same file.' which suggests that there's something in the file
at that point which is causing the error. This makes sense if it's a
conversion error.
The questions must be, therefore:
What is it converting? and
What is it trying to convert it to?
Time to go get some bytes out of that file. And make sure that you have
the right bytes! ;-)
Regards,
Fergus