I just did some checking on my code and found in all instances where I used the OLE-DB provider from ASP it has been read only. All table updates use VFP COM's called from ASP. When I tried an update from ASP I got the same error you described. I need to dig in to this a bit more. My feeble mind seems to remember actually testing this a few months ago.

>I think I misread you. I'm using DBC.
>Cetin
>
>>Just remembered, you are using a DBC and not free tables? I recall the OLE DB provider can read free tables OK but would not update.
>>
>>
>>>Thanks Michael. I checked them too and ODBC driver work w/o any problems on same data.
>>>Cetin
>>>
>>>>I've used the provider from ASP and ADO with no problems. Simple connection string "provider=vfpoledb.1; data source=c:\data\test.DBC;" worked fine.
>>>>Might be a permission problem with IIS.
>>>>
>>>>>Using ODBC I can update data from ASP. But whenever I try to use VFPOLEDB instead I get :
>>>>>'Cannot update the cursor' && If used with 'insert into ...'
>>>>>or :
>>>>>'Recordset doesn't support update. ...' && If used Addnew and update.
>>>>>As if it's readonly (or does really provider doesn't support updates from ASP?). I couldn't find much documentation about VFPOLEDB.
>>>>>
>>>>>I should be missing a very basic thing. Simply cannot see it. I've already tried connection.mode = adReadWrite, "Provider ... Mode=ReadWrite;", adUseClient,adUseServer, KeySet, ForwardOnly,Dynamic, Static adLock BatchOptimistic, Optimistic, Pessimistic combinations. Any help is appreciated. TIA.
>>>>>Cetin