I am not surprised by this - at least as far as ODBC goes. Chad's issue underscores why there needs to be a native VFP OLE-DB provider so that things exposed in the native VFP environment can be configured from non-VFP ADO clients.

>You can't call Stored Procedures from any ODBC code. The following
>also doesn't work:
>
>

> SELECT SomeStoredProc() fROM DUMMY where recno() = 1
>

>
>I thought it did, but it doesn't <s>...
>
>+++ Rick ---
>
>>Hi Chad...
>>
>>Are you looking for something that limits what updates do and don't go through - similar to what we have in views???
>>
>>My guess is that if something like this is available - it will be exposed in the properties collection of the RecordSet object. What this collection contains and what RecordSets and Connections in general are capable of doing - is determined by the provider.
>>
>>As far as I can tell, we cannot do something like this:
>>
>>oconnection = createobject("adodb.connection")
>>ocommand = createobject("adodb.command")
>>oconnection.Open("testvfp")
>>ocommand.activeconnection = oconnection
>>ocommand.commandtext = '=dbsetprop("view1","view","wheretype",2)'
>>ocommand.execute
>>
>>Perhaps the solution is to create a VFP COM Object that will do this work for you..