The recordset needs to have been obtained from the source in order for it to be updatable. It can probably be done by the conversion routine, but a snapshot of all the metadata information has to be saved so that a recordset can be rebuilt from it with all the properties from the source. Maybe you can contact the author of this utility and ask him to consider it.

If you want to do it without writing a file to disk, it can be done by using the same source but with a fake filter that would evaluate to a false and the result will be an empty recordset. You then take your data and populate this recordset with it. I've done this only for adding records and it works well, but in your case that's probably the same as just updating the original recordset itself without converting.

Working with the original recordset is not so bad either, unless you are editing a large amount of records. For small recordsets the differences might very well be negligible. Just my .02

>Hi Brian,
>>
>>Maybe following article could be of help. HOWTO: Using ADO Disconnected and Persisted Recordsets mskb #Q195082.
>>
>
>
>
>Hi Sergey,
>
>Thanks but I reviewed that, as well as most of the MSDN site yeasterday. It's also something JVP mentions in his Jumpstart article. I'd rather accomplish this without writing files to disk. It'd be tough to believe that I'd have to write a recordset update process, just seems like it would've been a common thing. I still have more playing around to do with both the VFPCOM and OleDbFox utilities.
>
>Hopefully this will be a native conversion in VFP 8.
>
>
>- Brian