Gentlemen,

Yes, it's SPT, I just referred to it as a view.

llRetval=TABLEUPDATE(2,.T.,"DetailView",Errors) returns .T., which I assume means everything was updated. It also means that my error routine, which relies on IF llRetval=.F. won't fire.

To Hiten Kishor: It's true, Foxpro will continue processing after an error if TABLEUPDATE(2) is issued, but it will not return .T. and it will propably record the error if cError variable is specified.

Anyway, I'm greatful for your involvement and the workaround.

*Snip
>>Yes, if that was what he was doing. Somehow, I don't think that was the case. I was real confused because at one point he said he was using SPT [first reply to Hiten Kishor].
>
>As I understood it, he used SPT to get the data.
>Made an updatable cursor with Table buffering.
>Made changes.
>Issued TableUpdate(2)
>Then was trying to handle the failed updates.
>I'd suggested looping and issuing the singleton TableUpdate(1) or TableRevert(.F.) on each hit as needed.
>
>Otherwise, endless loop!