Hillen Richard wrote:
> Using this proved datastack-method in the development environment,
> it´s ok;
> But after making a new standalone with "substacks moved in separate
> stackfiles" if I press the Save-button in stack Data I get "can´t open
> stack backup file".
With most commands which may fail for a wide range of reasons, it's
essential to check "the result" immediately after the command. For all
I/O it's especially helpful to include a call to the sysError function
so you can learn the specific error code the OS is delivering to LC.
e.g.:
save stack "SomeStack"
if the result is not empty then
answer the result &" ("& sysError() &")"
exit to top
end if
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
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
