>>>>I thought that this was fixed in VFP-7. I know the Wait Window command works but as far as forms I can't display them. Yet the OLE does not complain when I execute a DO FORM.
>>>>
>>>>Am I doing something wrong? If not, why is this such a big problem?
>>>>
>>>>Thanks
>>>>
>>>>Costas
>>>
>>>Hi Costas,
>>>
>>>What are you referring to exactly? What is your OLE - DLL or EXE?
>>>
>>>You cannot use any visual interface commands directly in DLL, but you can in out-of-process EXE.
>>
>>Its the same OLE I posted before. Out of process EXE. Instantiated using CreateObject().
>>
>>I wonder if I am doing something wrong here. The strange thing is that the form object gets created. However it does not get displayed. The visible flag is .t.
>>
>>Here is the code:
>>
>>define class Common as custom olepublic
>>* Compiled as Multi-Use OLE server.
>>* Instance variable declarations
>> dependent = .null.
>>
>> * Instance Methods
>> function changed()
>> * Save dependent object.
>> DO FORM form1 NAME frm Linked
>> READ events
>> this.dependent=frm
>>enddefine
>>
>>
>>The form1 is just a blank form. Any ideas?
>>
>>Costas
>
>My VFP 7 just hangs when I try to do that, saying that the other application is busy. I don't think it is a right idea to show the form from the COM. Why do you need to do that?

Yes, the READ EVENTS causes it to flake out. Do you think this a bug in VFP-7? Is there a bug list I can submit this to MS?

Anyway right now I am displaying the form as a regular EXE which of course works fine. I have to design callback methods in the OLE to recover the data needed for displaying.

Regards,

Costas