Hi!

I meant the COM object used in this particular case, if you follow the thread. Talking in general I would like to say 'You cannot see all PEMs of COM objects ...' ;) I know that type library definitions are visible to VFP debugger. In my tests in this thread, for example, main COM object properties are visible, but object created by SCATTER NAME and passed through COM in debugger appear with no properties.

Thanks for this note, it make things more clear.

>>Hi!
>>
>>You cannot see all PEMs of COM object in the debugger. You can access them, however. In VFP7 they appear both in debugger and array returned by AMEMBERS() function. So I just get object from COM object procedure call, than test: ? oRec.Field1, ... and see of all fields are passed. On my machine they're ALL passed, for sure, just not displayed in the debugger.
>>
>>HTH.
>
>Vlad,
>
>This isn't entirely correct. Since the object in this case doesn't have a type library item describing it, VFP doesn't "know" the properties until they're referenced. Once referenced, they appear in the debugger. A similar situation exists with some ActiveX controls such as the TreeView which have an hwnd property. Normally, you don't see it in the debugger. Once it's been referenced, however, it can found under the Object member of the control.