Hey John,
What I'm looking for is to control the conflict concurrency. Right now ADO seems to use all the fields in the where clause to find the record to update. This causes two things. First it will not be able to update the record if any of the fields have been changeed by another user. Second it is probably not the most efficeiant way to update a record.
If I could specify that it should use only the key field and the fields that have changed that should allow one person to change one field and me another without a conflict. Does that make sence?

>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..