Hi Mike,

I pass recordsets between VFP DLL's all the time. I've developed some VMP classes that might assist you in this endeavor. Let me know privately or send an email to evan@flextech.net if you would like to take a look at them.

Evan Pauley


>Hi!
>
>I had hoped I could ...
>
>1) Create an ADO record set in Excel or VFP and store it to a variable
>loAdo = CreateObject("ADODB.RecordSet")
>
>2) Call upon a method of a DLL made in VFP passing the ADO variable to fill in the ADO record set. This is the call I'm making in VFP...
>loProcessor = CreateObject("mydll.myobject")
>
>Inside ProcessData I...
>
>LPARAMETERS toADO
>IF NOT PEMSTATUS(toADO,"CURSORTYPE",5)
> RETURN .F.
>ENDIF
>
>So after all of this, the following prints a .F. on the screen
>
>?loProcessor.ProcessData(@loADO)
>
>Prior to calling loProcessor.ProcessData, loADO does have a cursortype property.
>
>Observation indicates that inside ProcessData, toADO is no longer an ADO recordset.
>
>Checking loADO after the ProcessData call shows that loADO is an object, but it no no longer has a cursortype property.
>
>COM is quite new to me. This works totally fine, when I don't compile the stuff into myDLL.dll
>
>What am I missing?
>
>Thanks!