>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?
>
>Hm, it's funny, when I NEED the C00000005 error, it isn't there - smirk!
>
>hs.

I wouldn't count on a C% error getting you out safely- what if MS fixes the problem that causes you a C5?

As far as quitting gracefully,

CANCEL
QUIT

does it for me every time, with no problems.