This could be a number of strings, such as "file not open for read" or
"file does not exist". There is no special string that indicates a
particular error, e.g. the errors don't all start with "error". You have
to check that the error is unexpected and doesn't contains "eof".
Kind regards,
Mark Schonewille
http://economy-x-talk.com
https://www.facebook.com/marksch
Buy the most extensive book on the
LiveCode language:
http://livecodebeginner.economy-x-talk.com
Op 30-Nov-16 om 01:12 schreef Peter Bogdanoff:
When I use:
read from file tURL until eof
to read from a file on disk, should I expect the <result> to always contain
“eof”?
I’m suspecting there could be a a file read error while reading thousands of
files and I want to catch that.What should I expect to see in the result when
that happens?
Peter Bogdanoff
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
