Hi Mark,

Some ActiveX controls could cause such problem. See Re: Problem with _Screen.ActiveForm.ActiveControl Message #503210 for possible workaround.

>I'm experimenting with an OCX that (in my limited experience) is exhibiting odd behavior in terms of the "ActiveForm" concept. Normally when I have put controls on a form (here I mean either VFP controls or OLE control), including, for example, the DHTMLEdit control, the reference to _screen.activeform references the VFP form object. If the OleControl is called "OleControl1", then you can get at it with _screen.activeform.OleControl1
>
>With this new OLE control, when the VFP form is instantiated, _screen.activeform instead refers to the OLE control, and the only way I can find to get to the VFP form object is with _screen.activeform.parent
>
>I don't understand why this is happening.