Hello,

I want a generic HTML page returned when a focexec returns an error. Any idea how this can be accomplished?

...
END
-RUN
-IF &FOCERRNUM NE 0 GOTO FOCERROR;

...

-EXIT

-FOCERROR
-HTMLFORM BEGIN
your HTML here
-HTMLFORM END

I just have a fex that can check &FOCERRNUM, &RECORDS, or &LINES that I -INCLUDE at the end of most fexes.
for example:
-SET &OUTPUT='HTML';
-IF &FOCERRNUM EQ 0 THEN GOTO NOERROR;
-NOLINES
TABLE FILE CAR
PRINT CAR NOPRINT
HEADING
"There was an error generating this report."
WHERE READLIMIT EQ 1
ON TABLE SET ONLINE-FMT &OUTPUT
ON TABLE SET PAGE NOPAGE
END
-RUN
-NOERROR

I tried the following and my error html page runs? I would expect it to exit before.

TABLE FILE CAR
PRINT *
END
-RUN
-IF &FOCERRNUM NE 0 GOTO FOCERROR;
-EXIT
-FOCERROR
-HTMLFORM BEGIN

Were Sorry!

&FOCERRNUM The document you requested cannot be found.

-HTMLFORM END

Sayed, as Gerry says, WYSIWYC..you're getting exactly what you coded.
the focerrnum for this bit of code is 757
0(FOC757) WARNING. YOU REQUESTED PRINT * OR COUNT * FOR A MULTIPATH FILE
The PRINT * and COUNT * commands cause the left-most path in a file
to be referenced. If the file has more than one path, data which is
not part of the left-most path is not printed or counted.

Do your test again, with a code snipped where the &FOCERRNUM is truly 0.

Hi Susannah,

I'm lost now. All I'm trying to do is send my users to a default error page if my code breaks on my PROD environment. I do not want them to see any FOC ERROR messeges.

For example I'd expect this code to break and then go to my error page only

TABLE FILE CAR
printt *
END

Sayed,

This code will produce an error (check the source code within the HTML via context menu - right click)

TABLE FILE CAR
PRINT *
END
-RUN

This should not (unless you do not have the CAR file mas and foc in your path!!)

TABLE FILE CAR
PRINT COUNTRY
END
-RUN

The reason, as Susannah has already mentioned, is that the PRINT * against the CAR file would produce a selection against a multiple path and it has always been that FOCUS produces an internal error for this, even if it is a warning!

Your last example

TABLE FILE CAR
printt *
END
-RUN

Would produce a syntax error. This is not the only type of error you should be checking for.
Apart from the fact that, if you put code like that into your live environment, it would show a distinct lack of testing being done beforehand!!
Check for errors that could occur in live, such as file not found, EDA down, security error etc. etc.

T

Thanks for the clarity Tony. So I can still have &FOCERRNUM NE 0 when my focexec runs and return a report?

I was expecting &FOCERRNUM EQ 0 whenever I get a report back otherwise trap the error and send users to a default error page.

when you have written your report imperfectly, yes you'll get a &FOCERRNUM >0. So be sure to TEST your reports to determine their &FOCERRNUM, and whether or not it is acceptable to you, before putting them in to production, if you plan to use &FOCERRNUM as a branching determinant.

Thank You ALL for your suggestions. It has been a great help.