>Howdy all --
>
>I have given this problem additional thought, trying to find a workaround that will help those who keep getting blown away by these frustrating 'Buffer Overrun" problems.
>

Just a thought: Is there a way to identify the problem classes automatically (i.e., is there a pattern within the class that could flag the different processing automatically)? Remembering to turn the manual option off and back on again when needed will use additional "brain cycles" and "attention energy," which is never a good thing -- those should be reserved for the work at hand.

On another topic: Is there any way to avoid the significant slowdown with PEM Editor when the debugger is active? Not a show stopper like a buffer overrun crash, but an annoyance nevertheless.