Does anyone know of a way to surpress the error message "Regular expression error nr..." that appears in the BW window when the program tries to do an expr.compile on an invalid expression? We want to use our own error handling for this scenario.

Thanks,
Francis

I found some info on the compiler flags, I hope everyone will find it useful...

Use these numbers as w1,w2.................... For selectively filtering the warnings during compilation of scripts..................

1 - Declared but never used
2 - Function never used
3 - Return value of function ignored
4 - A long divided by a long also gives a long.
5 - Statement/Label not reached.
9 - Passing external variables as call by reference to
function.
10 - Passing fixed variable to non-fixed call by reference
argument. (or non-fixed to fixed)
11 - bic6.1 compiled with -DLEXDEBUG. (slower)
12 - External variable declared inside function
added in external symbol table
13 - System library <bic_stdlib> ignored.
14 - Compiler buffer too small for post optimalisation
15 - Warning given by #pragma warning <text>
16 - Missing selectdo; automatic break
17 - #undef: Macro '%s' not defined
18 - Macro '%s' redefined
19 - Function '%s' double defined in DLL '%s'.
20 - link.on.stack() used as call by reference.

Prashanth,

That is nice information to have. Perhaps not appropriate in this situation. Francishsu needs a way to avoid runtime errors ("white screen errors") with expr.compile. I did not have much to offer, because I started experimenting with expr.compile very recently.

Francishsu, did you try error.bypass? I know that works with db errors.

We did try setting ERROR.BYPASS = 1 before the call to expr.compile(). Unfortunately, it didn't make a difference.

Have you tried to define an "on error:" program section. Try which is the value assigned to variable e when an error ocurrs???