Steve,

If you are using ADO to execute queries, then both Execute methods of Connection and Command objects has RecordsAffected parameters. Note that this parameter returns number of affected records only for non result-returning queries. Otherwise you can use Recordset.RecordCount property. If query cannot be executed you'll get an OLE error message from OLEDB provider.

>I'm not sure that will work. Check this out:
>

>Use "C:\Program Files\Microsoft Visual FoxPro 8\Samples\Northwind\employeeterritories.dbf" In 0
>Select EmployeeTerritories
>? CursorSetProp("Buffering",5)
>Update EmployeeTerritories Set TerritoryId=999999999 Where EmployeeId = 99999
>

>
>If I am in the IDE with my talk/status settings, I get the message
>

>Updated 0 records in 0.02 seconds
>

>
>But that's not necessarily a VFP "error". How would you trap for that message otherwise - is it possible to throw some kind of exception or get a MSSQL-esque @@rowcount from the response.
>
>My non-VFP app would otherwise be doing inserts all day, not knowing that VFP is actually throwing everything away, quietly.
>
>
>
>Thanks.
>
>
>>It makes sense that _TALLY would not be available because the processing occurs in the OLE DB provider. I usually assume everything worked unless I get an error back.
>>
>>
>>>I am running a SQL-Update over OLEDB, and the _tally variable is not available. Can anyone recommend a way to tell if an Update / Set has been successful other than following the Update with a SQL-Select?
>>>
>>>Thanks.