Thanks Viv. It seems that the debugger even interrupts within try-catch-endtry constructs? Talking about "being careful for what your are asking for"? :)


>The debugger can be configured to break on an exception before any handler is invoked (i.e it overrides your coded exception handling)
>Open the Debug/Exception... dialog from the menu to check/modify which exceptions are caught in this way
>
>Read this (and related links) for more info:http://msdn.microsoft.com/en-us/library/x85tt0dd.aspx
>
>>>Does it even trap the exception? Do you throw the exeption to the previous exception handler?
>>>
>>Well it just interrupts the method it is in and just leaves, but continues at the next step after the call to the method where the terminal error occurred.
>>
>>Thanks.
>>
>>>>In "runtime" I don't seem to have a problem. I install a "global" error handler, and in case of unsupported errors, it triggers the errorhandler.... well most of the time.
>>>>
>>>>When I execute code in development, and there is an error, rather throwing a system (default) error; or appropriately call my errorhandler, the system seems to leave the method it is in and just continues.
>>>>
>>>>Is there a method of operation that solves this?
>>>>
>>>>Thanks.