Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Appeon Web handling of OLEObject errors

  1. Issue
0
Votes
Undo
  1. Daniel Vivier
    Daniel Vivier
  2. PowerBuilder
  3. Thursday, 31 August 2017 14:50 PM UTC

As I understand it, none of the traditional PB methods of catching and handling OLEObject errors are available in Appeon Web, like try/catch blocks, the ExternalException event, and the SystemError event.

I understand that Appeon Web does its own handling of such errors somehow, but could someone please explain what it actually does? I presume there's a messagebox, but then is it ignored? Or does it crash the program (as an unhandled exception would in PB)? Or what?

Thanks.

  1. PowerServer Web
Standalone mobile application & Powerserver connec...
Migrate from PB12.6 to PB2017 - Issue with PBNISMT...
Responses (3)
Appeon Support Team
Appeon Support Team Accepted Answer Pending Moderation
  1. Monday, 11 September 2017 03:19 AM UTC
  2. PowerBuilder
  3. # 1

Hi,

We don't have a feasible workaround for this currently. But we will record it as a requirement in our CR pool, I will get back to you once we have a plan to support this feature.

Regards,
ZhaoKa

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Monday, 11 September 2017 14:15 PM UTC
ZhaoKa, could you please at least tell us how it is actually handled in Appeon Web now? When there is an error, what does the application do? Give a message? Exit? Continue? Surely that minimal information should be available, and should be included in the documentation (which it isn't!).

  1. Helpful
There are no comments made yet.
Daniel Vivier
Daniel Vivier Accepted Answer Pending Moderation
  1. Thursday, 31 August 2017 20:54 PM UTC
  2. PowerBuilder
  3. # 2

I don't understand why try/catch/finally can't be supported - it definitely exists in JavaScript. I just tested the following script to access some dBase data with ADO within an HTML web page, running in IE, and it worked perfectly, including nicely handling any errors with the alert in the catch clause: