|
Hi Terry, Can it be something as basic as MB needing to have a proper statement after each label ? Try moving your ERR_RESUME label to just before the Exit Sub prior to the error handling lines. That's where I always put my exit label, and it works. Best regards / Med venlig hilsen Lars I. Nielsen GisPro Terry McDonnell wrote: I've just started to put error handling in my finished system, to bullet-proof it, and this is the 1st time I've used the feature in MB.Simple question: Does an OnError event (dealt with in a handler) ALWAYS result in the program bombing out afterwards? I want non-fatal errors to be reported to the user but to allow them to continue. To this end I've done as the following: ---------------------------------------------------- ' End of a sub with a loop, in which error happens Exit sub ERR_RZSTOPS: llAbort = ERROR_REPORT( Err(), Error$(), "SHOW_STOPS_TOO - Can't get Route's Stops", FALSE) Resume ERR_RESUME ERR_STOPS: llAbort = ERROR_REPORT( Err(), Error$(), "SHOW_STOPS_TOO - Can't get Route's Stops' Counties", FALSE) Resume ERR_RESUME ERR_RUNORDER: llAbort = ERROR_REPORT( Err(), Error$(), "SHOW_STOPS_TOO - Can't get Route's Stops' Running order", FALSE) Resume ERR_RESUME ERR_RESUME: End Sub ---------------------------------------------------- So I assumed that after each error handler, the prog will resume at the label ERR_RESUME:, where the next statement is "End Sub". Hence the code would "drop out" of the sub and return to the command following that which called it. Instead, the screen clears, all my tools and menus disappear and MI returns to native mode. 'ppreciate it Terry McDonnell _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l |
_______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
