Yuri,
ADODB behavior is changed in .NET (pay attention reference you add is a wrapper not the ADODB you use in VB and VFP). I don't know the details but I remember documented with MDAC 2.8
I don't feel as an expert when it's .Net but still would dare to suggest to switch to dataadapter or another similar technique like table data gateway.
ADODB cursors has no place in .Net it seems (sounds as if only supported to ease migration).
I think you'd be happy hearing this:)
I was generally going nuts with ADODB but much more comfortable with DataAdapter, DataReader etc.
ADODB was hiding open/close of connection behind the scenes, with ADO.Net you know when they're open/closed etc.
It was harder to define hierarchical sets, convert to and from XML etc etc.
It has been painfull to me too but I suggest you to forget ADODB as quickly as possible (and I feel that .Net forcefully will make all ADODB useless sooner or later).
Cetin

>Cetin,
>
>I was long under the impression that the ADO recordset gives me more control on its properties and deeper understanding of what is going than the cursor adapter (in VFP).
>Now, when I am required to work in VB.NET instead of FoxPro, I try to use the same concept (especially when the code has already been developed in FoxPro, proved to work nicely there, and it seems easy to use the code directly in VB.NET with minor syntax changes).
>
>It looks like I do not have this option anymore. In VB.NET, besides the problem with the recordset.source, I am not able to update VFP table. With both, recordset.UpdateBatch or Update, either there are no errors, or the error description is confusing:
>
>“Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype.”
>
>Because updates work properly for the “selected locktype” in VFP and VB, then I assume that it is the “limitation of the provider”.
>
>Looks like I need to use the Data Adapter here anyway.
>
>I will appreciate your opinion.
>
>>Yes,
>>had problem in setting .source. I don't know if it's a bug or not and honestly didn't even think to use ADODB in .Net until seeing your question.
>>Cetin