>>>>Something weird is happening when I am calling a form from another form. When called with DO FORM myFormName from a button's click event on the calling form it goes to the load event of the called form...everything cool so far, then the weirdness happens. Instead of going to init() it goes right to unload() event, closes and returns to the calling form bypassing everything. This called form does indeed load from other areas of my application, even when called from other forms, but when being called from this particular form it is not loading, just fires the load event (which has nothing in it) and then it goes to the unload event and skips init() activate() etc. and then closes. whatup? anybody have any ideas?
>>>>
>>>>Thanks.
>>>>
>>>>John.
>>>
>>>Just a guess, but it might be a form control whose .Init did execute properly causing the form to shut itself down and leave.
>>>
>>>Steve
>>
>>Hi Steve,
>>
>>I 'set step on' in the load event of the form, and the very next stop the debugger makes is at the unload event of the form which seems to have bypassed all other events. How rude!
>>
>>John.
>
>SET COVERAGE to some file in the load event. See if does go right to the unload or where it might go.
>
>Steve

Thanks everyone for helping out! I'm not VFPing as much as I used to, so fixing this problem took me into areas I haven't been in for some time. All of the information I received is knowledged gained. Okay, on to the fix. Yes, C.R it was a data issue, not in the DE but in an updatable cursor that populates a grid. I forgot to add a logical field set to .T. in the cursor (SELE .T. AS checkme, mytable.* blah blah blah). This was indeed the problem, but I still don't understand why my grid that was expecting the logical field wouldn't report the error. Steve, I haven't used SET COVERAGE before, but would this have captured where exactly I was having problems because set step on in the debugger sure wasn't very helpful with this one?

Thanks again everyone : )

John.