>>I would like to trap connection errors myself instead of presenting users with the system dialog box that quotes the error message and provides OK, Revert, and Help buttons. But I can't seem to get rid of it. Here's the setup:
>>
>>SQL Server table has a unique index on one field. VFP app uses a remote updateable view of this table (created in code, not in a .dbc). dispWarnings for the connection is set to false. If user enters a duplicate value in the grid and changes rows, the system dialog box fires. I would think that I could use tableupdate() and aerror() in the beforeRowColChange event to handle the error myself, but the dialog box beats me to the punch every time.
>>
>>Is there any way to suppress that dialog box?
>
>There is a parameter in the SQLSetProp() function to turn off the display of connection errors. Then use aErrors() to see what the last error, if any, was.

That ought to work, but it doesn't. DispWarnings is set to false. Same result.