>>I get Error 1651 alot when debugging events: "CANCEL or SUSPEND is not

>I've only seen this when I put this in something called by a report.
>
>Are you sure that is not the case here? I put "Suspend" in Destroy events all the time.

After a little more experimentation, I found out that I am getting the suspend problem only when clicking the close of the FoxPro application (the little x at the very top right of my running application) when I have a form up. If I click on the close of the form I can suspend inside the QueryUnload, no problem. BTW, I'm using Mere Mortals.

I guess that FoxPro is sending the event that is closing the form and has decreed that this event is non-suspendable? Anyway, I can debug now as long as I click close on my form instead.

Thanks.
-Dave