>
>Fabio,
>
>What is the behavior you expect? ASSERT is for testing and debugging applications. It has no affect in a compiled application.
>
>
>Exactly for this reason.
>
>I want a suspend on code, a output dialog with four buttons, ( like MessageBox )
>WITHOUT ANY EVENT !
>
>If you run my code, with ASSERT on AfterRCC,
>if you push ignore, i want'n see the reactivation infinite loop ( you see the print activate lines ).
>
>This is so obvious, that it seems absurd to have to me to demand it.
>
Fabio,

You can't expect the assert dialog FoxPro presents to behave the exactly same way that the MESSAGEBOX() works. The assert dialog is a child window of VFP, MESSAGEBOX() is not. Further, any form being run in design mode isn't the same as the one that's created at runtime.