[Openroad-users] OpenROAD runtime error handling

[Neil.Warnock at luminary.co.uk]

See PROCEXEC.SetExitTrap() and SESSIONOBJECT.ClearErrorFlag(). Not quite
what you want but implicit and explicit EXITs can be trapped and handled
gracefully using these.

 

Neil Warnock
Luminary Solutions
Tel: +44 (0)845 371 4090
Mob: +44 (0)771 265 0291  
Email: Neil.Warnock at luminary.co.uk

For more information on Luminary go to http://www.luminary.co.uk
Luminary Solutions Limited Registered in England No 4854134 VAT Reg No.
829 3166 13
Registered Office: 16/17 Pavilion Business Park, Royds Hall Road, Leeds
LS12 6AJ

 

-----Original Message-----
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Robert
Allely
Sent: 18 June 2007 23:07
To: International OpenROAD Users
Subject: [Openroad-users] OpenROAD runtime error handling

Is there a good way to trap run time errors - which seem to only appear
in the w4gl log and trace window - so the user can see that something
has gone wrong without having to look at the trace window? I was
thinking of a setting like DBMSErrorPrinting .

Robert Allely
Ports of Auckland Ltd
NZ
***
This e-mail is privileged and confidential.  If you are not the intended
recipient please delete the message and notify the sender at Ports of
Auckland Limited.
***

________________________________________________________________
OpenROAD-Users mailing list

You can maintain your subscription here:
http://www.peerlessit.com/mailman/listinfo/openroad-users

To unsubscribe click on this link
mailto:openroad-users-unsubscribe at peerlessit.com&subject=unsubscribe

To subscribe click on this link
mailto:openroad-users-subscribe at peerlessit.com&subject=subscribe