A technique that you can use now to generate a C5 error may not work in the future after MS has fixed the error. C5 bugs are not (aren't they really? :) ) part of the design of the product, thus you cannot rely on them to build your application upon.

If your application is caught in a endless error loop, the user can kill it with the three fingers salute (CTRL-ALT-DEL, End task).

---

>I have often situations where error handlers go into endless loops, such as Can't Release Object, Do you want to Continue Yes/NO, xxx is not an object, Can't release Object, Do you want to Continue Yes/NO etc. etc.
>
>I figure in situations like these it would be good to give the user another option, CANCEL and it would just execute some code that will bail out FOR SURE. I tried QUIT and CLEAR ALL, QUIT etc. or releasing the main application object, but they just continue with endless error loops.
>
>What would be a simple code THAT GENERATES A C0000005 GPF FOR SURE? Then I could give the user the option to run that code and the program will exit for sure?