Errsysw not working

[TimStone]

I'm overlooking something, but perhaps you can refresh my memory.

Using FWH, Harbour, and Visual Studio Community.

In my main application, I include errsysw.prg and it works perfectly when an error occurs.

I have a subset of my program, using many of the exact same files from the same source directory. When an error occurs, instead of errsysw showing a popup screen with the error and all the data, the program just sends the steps to an hb_out.log file.

I must be overlooking a setting somewhere. Any ideas would be appreciated.

It is NOT a problem with the errsysw.prg, nor is it a problem with Harbour or FWH. It occurs like this on all messages, so errsysw.prg is simply not being triggered.

Thanks.

[Antonio Linares]

Tim,

Are you calling ErrorBlock( { | oError | MyErrorSystem( oError ) } ) from your main PRG ?

function MyErrorSystem() is a function provided in your own errsysw.prg

[hmpaquito]

Hi,

Critical errors do not invoke the standard error system

Show hb_out.log

regards

[Marc Venken]

Tim,

Are you calling ErrorBlock( { | oError | MyErrorSystem( oError ) } ) from your main PRG ?

function MyErrorSystem() is a function provided in your own errsysw.prg

In the source dir. there are 2 errorsys prg's. one is more extended but the filename = errsysw_.prg (this program has been a older topic on the forum, but seems to be a enhanced version.

It seems that some programmers here in the forum prefer there own build errorsys. What would be the preference ?

[Antonio Linares]

Tim,

Please post the hb_out.log content here

Marc,

You an use your own customized error dialog box, send an email, etc

[TimStone]

RESOLVED

My error. I have one variable I'm tracking, which I report in the customized error log, and it wasn't in the sub-version of the program. Thus it was causing the errsysw.prg to error within itself.

All is good now ...