Hi David,

>1. I am having some trouble with the VFPCom.CursorToRS() function. The problem is that it creates the recordset with the wrong field attributes eg memo ado constant is 201 but it makes it 129 and sets the defined length to 256 so then the data gets truncated.
>
>2. The next problem is that when you have multiple memo fields but you only fill in one memo field of the cursor, when running the cursortors() it replicates the data from the memo field filled in to the other memo fields even though they are blank. We're using VFP7 with the COMUtils we also set the null values on all memo fields. We came across these problem when setting the recordset data for the crystal reports.
>

I too have run into these same problems when using VFPCOM.CursorToRs() to pass ADO recordsets to a Crystal Report. I've spend more than a few hours on this issue and wish I would have seen your post a few weeks ago. It may have saved me at least a couple of the headaches I obtained from beating my head against the wall on this Memo/Text field issue. :-)

I sincerely hope that the new version of VFPCOM.DLL that is due out RSN will resolve these issues with Memo/Text type fields.