Hi!

Ok, after some tests I see it works. However, debugger just do not display any property, you can just access it and get values or assign them.

The problem in Kevin's case is quite strange than. Kevin, how did you compiled that COM object project? Do you use it as EXE, single-threaded DLL or multi-threaded DLL? What version of VFP you use?


>Hi,
>You said you couldn't pass objects back and forth between COM objects and applications that called them if they participated in different memory spaces. I said you can. In-process COM objects participate in the same memory space. Out-of-process COM objects don't. But you know that. :-) However, in both scenarios, objects can be passed back and forth to each other. They are simply converted/copied to COM objects when they are "passed" through the COM barrier.
>
>>Hi!
>>
>>I know that, but in the case described in this thread DCOM is not used. Or did I missed something, Kevin?
>>
>>>Vlad,
>>>I disagree totally with the statements below. What is DCOM? Among other things, it gives you the ability to pass object references across process barriers. There is an added layer of marshalling that needs to take place but this has been built into DCOM.
>>>
>>>>Hi!
>>>>
>>>>Because this is the DLL, it could run in another memory space. In such case passing objects is not possible from COM object to calling application and back. It is possible only when DLL runs in the same memory space, in other words, if COM object is a single-threaded In-Process COM object.