Hi Alan

You're right! Pemstatus doesn't work. That's awful! OTOH I can use type("toADO.CursorType") = "U" to detect if the object is not an ADO set.

Thanks!

>Mike, it probably is working. The problem is with pemstatus(). Change your code to:
>
>

LPARAMETERS toADO
>  Return toAdo.CursorType
>

>and see what happens. Set the cursortype of the recordset you're passing and see if they match up. They should.
>
>Alan
>
>>Hi
>>
>>Unfortunately, passing it as a "regular" parameter does not seem to be working. Please read the original post.
>>
>>>You just pass it as a regular parameter. There is no specific step involved.
>>>
>>>>Hi Hector
>>>>
>>>>Maybe I should rephrase. How can I pass an ADO recordset to a VFP dll for subsequent processing?
>>>>
>>>>Thanks!
>>>>
>>>>>>Checking loADO after the ProcessData call shows that
>>>>>> loADO is an object, but it no no longer has a
>>>>>> cursortype property.
>>>>>Have you checked to see if you have access to other properties and/or methods of loADO from inside ProcessData? I mean, are all properties/methods gone or only that particular property (cursortype) is gone?
>>>>>
>>>>>On a second thought, I am not sure how PEMSTATUS works on COM objects. For example, I have seen that the debug does not show all properties and methods for a COM object (or an ActiveX control) until they have been referenced in code. Could it be that PEMSTATUS have a similar behavior?