I would do it too, but it doesn't work, TableUpdate() always return .T. in any update error. I test it by myself too... Here's Focus Magazine say's about it...

"As with the native CursorAdapter, most errors are trappable in the "traditional" way ? test the return value of TableUpdate and, in case of failure, use AError to determine the cause. Unfortunately, the detection of an update conflict is also a problem for the ODBC type CursorAdapter."

>You would handle it just like any other error when managing remote data.

lnRetVal = tableupdate()
if lnRetVal < 0
   aerror(laErrors)
   * error processing here
endif

>>I've read the Focus Article:
>>
>>http://www.code-magazine.com/focus/article.aspx?quickid=0301062&page=4
>>
>>But I don't like the solution showed in this issue, If CA can't handle ODBCs errors it's not a solution for me (and I think a lot more), I was thinking CA's a good concept, but not a solution for Universal connection if can't handle errors... I'd consider this issue as a Bug with an only-few-servers-Workaround.