I have a standalone (MC 2.3.2 for Win32) that I suspect encountered an error and displayed the execution error stack. I say "suspect" because I think it might have been hidden by another stack such that the app appeared hung. Is there a way to make sure the error stack is top most? If not, what happens if I don't include the execution error stack in my standalone? Is the statement ignored and execution continues or does the handler exit? I never know what sections of code the errors might pop up in so I don't want to litter my code with tons of try/catch combos. The few times I get errors in the standalone I would like to log them to a file for review later. Maybe just a top level dialog that informs the operator to contact the system administrator and the system would continue to run, ignoring the message the app received from the remote computer that caused the error. This application has run for several years 24x7x365 as a SuperCard standalone application on the Mac platform with only a handful of script errors over its life. I hope to reproduce that kind of reliability with my MC version on Windows 2000. Larry Huisingh Archives: http://www.mail-archive.com/[email protected]/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
