Bob -
You check it as follows:
1) Set the error variable. The error variable contains 0 if no error
occured and an integer greater than zero when an error or a failure to find
data has occurred.
SET ERROR VARIABLE OFF
SET ERROR VARIABLE verrx
2) Execute the command where the error you want to check may occur.
.........
3) Immediately test the error variable verrx. It is reset with each command
executed and you must test verrx directly or save it for testing later in
the very next command after the command in question.
SELECT xxx FROM table_name INTO vxxx WHERE xxx = .vyyy AND LIMIT = 1
IF verrx = 2069 THEN
whatever ..........
ENDIF
which is the immediate test or save the error variable from the SELECT
command for later testing like this:
SELECT xxx FROM table_name INTO vxxx WHERE xxx = .vyyy AND LIMIT = 1
SET VAR verrx_save INT = .verrx
You can then check the value in verrx_save against a table of error
conditions to get the exact error condition which was generated when the
command in question was executed.
=======================================
At 01:38 PM 9/27/2001 -0400, you wrote:
>
>Hello Everyone:
>
> I think I remember see either on this list serve or
>in my reading a way to check for an actual error code
>condition.
>
>I think it went something like :
>IF ON ERROR(947) etc.
>
>Does anyone know about this?
>----------------------
>Bob Powell
>The Hotchkiss School
>Lakeville, Connecticut
>Systems Administrator
>[EMAIL PROTECTED]
>
>
>
>
