>ADO is a good solution, but if you don't want to do it, there are a couple of alternatives:

ADO seems to work but untill now I've tried converting a ADO recordset into a cursor using VFPCOM but it return an -10 instead of doing the convert. Converting a cursor into a record set works but it doesn't seem to be very fast.


>
>Rick Strahl's wwIPStuff class has 2 very cool methods: EncodeDBF and DecodeDBF that take a table and convert it to a string for exactly the purpose you want it for.

I think this is exactly what I'm looking for ...

>On the client side, if you are going directly back to dbf, (it sounds like you are) then use the same XML class to convert the document back ot a table.
>
>EncodeDBF is faster, but I like the XML solution because down the road, any client can use it.

I think XML is indead the most generic solution, but yes indeed (bis), only me (and VFP) will need the results so I think I'll go for EncodeDBF ...

Thanks for the advice ...