Bob Sneidar wrote:
On Sep 30, 2014, at 09:13 , Richard Gaskin wrote:To diagnose problems with file access (and many other circumstances where error-checking is useful), check the result after attempting the action. With file access it can be very help to include a call to sysError there, so you can see what the OS is complaining about, .e.g: open file theDestFile for binary write if the result is not empty then answer the result &"("& sysError() &")" end ifThanks Richard. I get “Can’t open that file.” in the result for the write. Very informative. ;-) Now I have to figure out *why* it can’t open that file.
What was the OS error number returned from sysError()? -- Richard Gaskin Fourth World Systems LiveCode training and consulting: http://www.fourthworld.com Webzine for LiveCode developers: http://www.LiveCodeJournal.com Follow me on Twitter: http://twitter.com/FourthWorldSys _______________________________________________ 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
