Thanks Vlad,

RE: >I guess this is because old events loop for old forms do not support the ActiveX controls. ActiveX can work only with new common VFP events loop by READ EVENTS command (I meant Windows events handling loop).

This is kind of what I was thinking.

The reason it's not feasible is actually quite simple: Our application allows for the development of electronic forms. These electronic forms are built with our own tools, and saved as a table, but not in the same form as the scx/sct. So, the component of our application that renders these screens would have to be altered. This is a huge piece of code that we have inherited.

We will probably have to go this route, but I wanted to post this message to see if anyone has run into this before, and might have a "quick" fix for it.

Thanks

>Hi!
>
>>OK. This is going to sound like an odd one, but I have a situation where we have some FoxPro 2.6 screens still being used in our VFP 6 application. We have many forms that use ActiveX controls.
>>
>>Here is the problem:
>>
>>Whenever one of the old FoxPro 2.6 screens is running and one of the VFP forms with an ActiveX control on it is launched, the ActiveX control is visible but doesn't function at all. It's like none of it's events are firing. You can click on it, but nothing happens. It behaves as if you never clicked on it.
>>
>
>I guess this is because old events loop for old forms do not support the ActiveX controls. ActiveX can work only with new common VFP events loop by READ EVENTS command (I meant Windows events handling loop).
>
>>For business purposes, it isnt' feasible to convert these FoxPro 2.6 screens to VFP forms. Has anyone had any experience with this? Any ideas? Anything?
>
>Why it is not feasible? I know very little of problems when converting 1 to 1.