Hi Al,

I'm talking retrieving data from and sending data to SQL server using SQL server stored procedures. With this in mind, I am trying to establish where/how I can harness the automatic conflict resolution that VFP offers with remote views.

Regards,


>>Hi,
>>
>>When using remote views, you can set the WhereType value to one of the following --
>>
>>DB_KEY
>>DB_KEYANDUPDATABLE
>>DB_KEYANDMODIFIED (the default)
>>DB_KEYANDTIMESTAMP
>>
>>This is fine and very convenient when using views. However, I have a requirement to provide an all round retrieve/update solution to SQL server using stored procedures only. For this, I am creating a data access subclass in my framework for cursor types in Fox created solely by sprocs.
>>
>>Apart from writing application based conflict resolution code into the sprocs which I don't really want to do), how can the functionality provided by VFP with remote views be "utilised" or tapped into when using sprocs? Does Fox find this functionality from within the ODBC driver? If so, how can it be accessed?
>>
>>So, in a nut-shell, I would like to be able to send an update back to the SQL server using a sproc and have ODBC tell me when there has been some form of conflict on the server.
>
>Not really sure what you're after here. I assume you're talking about the case where you retrieve a row from SQL server, edit it, then send it back but in the meantime the same row has been modified or deleted by someone else.
>
>Are you talking about VFP stored procedures, or SQL Server stored procedures?