The CursorAdapter datasource is the connection handle. No problem.

So the only issue you have is identifying your memofields. If you a) have them uniquely identified (e.g., mMyMemo) or have an active data dictionary, use that information to "map" those fields to Memo data type in VFP. And if not, that information is easy enough to pull from your DBC either dynamically or once, the latter into a cTable, cField table you package into your EXE. That information is used to map from the backend to the CA.

Hank

>>I gather you didn't "wrap" the sqlexec command? If so, then making it create the CA on the fly would solve the issue.
>>
>>>>Antonio,
>>>>
>>>>Thank you for the explanation. Am I correct to assume that if their organization were using Cursor Adapter, making change from ODBC to OleDb would be possible (without a major rewrite)?
>>>
>>>I think yes, if we would use CA for data access, then switch between drivers would have been easier.
>
>We have our function around sqlexec (in both dll and our VFP apps). How would we convert it on the fly (we're using ODBC connection and re-use same handle for all commands).