Confirming a Save command

[FlexibleLearning at aol.com]

Always a good idea to test 'the result' after a save command. One client 
complained his program didn't save after copying a stack from a CDROM (which, 
of course, had a read-only property). Another had a server problem which 
sometimes allowed a save, and then didn't. The doSave below forced him to 
accept it was his problem, not mine. Anyway, a simple generic handler in the 
stack script may help you...

on doSave
  save this stack
  if the result<>"" then answer "Save error... You cannot write to CDROM. 
Please select a different folder, then try again" with "OK"
end doSave

If you want more a accurate reason, check if the SysError is not 0.

/H


_________________________________________________
Hugh Senior
The Flexible Learning Company
Consultant Programming & Software Solutions
Fax/Voice: +44 (0)1483.27 87 27
Email: <A HREF="mailto:admin at flexibleLearning.com">mailto:h at flexibleLearning.com</A>
Web: <A HREF="http://www.flexiblelearning.com/">www.flexibleLearning.com</A>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.runrev.com/pipermail/metacard/attachments/20020916/b03181ea/attachment.htm