That's right. ODBC errors, which have a type of 1526, get picked up by AERROR() but not by the error handler. I'm wondering if the DispWarnings property works only on remote views created in a VFP database and not in remote views created in code.


>Hmm. I'm perplexed. Do you mean that if you set ON ERROR TO some function of your own that it doesn't get called when you violate index uniqueness?
>
>>Thanks, Nancy. That's what I'd like to accomplish, but VFP's ON ERROR handler doesn't trap type 1526 errors. The docs say to use AERROR(), but by that time it's too late--the system dialog box has already fired. I have this problem only if the user is working in a grid and calls the implicit tableupdate() by moving the record pointer; calling TABLEUPDATE() from code works fine, unless the tableupdate() call is in the beforeRowColChange method, in which case the pesky dialog box still fires.
>>