The OpenEdge client aborts silently with a STOP condition if an error occurs while a database remote server was resolving a query on behalf of the client

The OpenEdge client aborts silently with a STOP condition if an error occurs while a database remote server was resolving a query on behalf of the client.

Oct 20, 2015
Knowledge

Title

URL Name

The-OpenEdge-client-aborts-silently-with-a-STOP-condition-if-an-error-occurs-while-a-database-remote-server-was-resolving-a-query-on-behalf-of-the-client

Article Number

000187960

Environment

Product: OpenEdge Version: 10.x , 11.x Product: Progress Version: 9.1E OS: All supported platforms

Question/Problem Description

The OpenEdge client aborts silently with a STOP condition if an error occurs while a database remote server was resolving a query on behalf of the client.
If an error occurs while a database remote server was resolving a query on behalf of a client, the error message is not forwarded to the client.

Steps to Reproduce

Clarifying Information

The issue can be reproduced using the following code against a database called "test" with a CHARACTER field called "valc":

RUN PROCEDURE_test.

PROCEDURE PROCEDURE_test :
IF NOT CAN-FIND (FIRST test) THEN DO TRANSACTION :
CREATE test.
ASSIGN test.valc = "1" .
CREATE test.
ASSIGN test.valc = "2#" .
CREATE test.
ASSIGN test.valc = "3" .
END.

FOR EACH test WHERE INTEGER(test.valc) > 0 NO-LOCK :
MESSAGE "valc: " test.valc
VIEW-AS ALERT-BOX INFO BUTTONS OK.
END.
END PROCEDURE .

Error Message

Defect Number

Enhancement Number

Cause

This is expected behavior. The error is happening during server selection and the database remote server does not have the capability of sending the actual errors raised during expression/selection evaluation to the client. In those cases, the errors go to the database log file and the client raises a STOP condition.

Resolution

Trap the STOP condition and return a standard error message. For example:

RUN PROCEDURE_test NO-ERROR.

IF RETURN-VALUE > "" THEN
MESSAGE RETURN-VALUE
VIEW-AS ALERT-BOX INFO BUTTONS OK.

PROCEDURE PROCEDURE_test :
IF NOT CAN-FIND (FIRST test) THEN DO TRANSACTION :
CREATE test.
ASSIGN test.valc = "1" .
CREATE test.
ASSIGN test.valc = "2#" .
CREATE test.
ASSIGN test.valc = "3" .
END.

DO ON STOP UNDO, RETURN ERROR "STOP condition triggered!!! See database log file for exact error message.":
FOR EACH test WHERE INTEGER(test.valc) > 0 NO-LOCK :
MESSAGE "valc: " test.valc
VIEW-AS ALERT-BOX INFO BUTTONS OK.
END.
END.
END PROCEDURE .

Workaround

Force the query to be resolved by the client as opposed to the database remote server, for example:

FOR EACH test NO-LOCK:
IF INTEGER(test.valc) > 0 THEN DO:
MESSAGE "WA valc: " test.valc
VIEW-AS ALERT-BOX INFO BUTTONS OK.
END.
END.

Notes

Keyword Phrase

Last Modified Date

11/9/2015 3:01 PM

The OpenEdge client aborts silently with a STOP condition if an error occurs while a database remote server was resolving a query on behalf of the client

Files(0)

Was this article helpful?

Was this article helpful?

The OpenEdge client aborts silently with a STOP condition if an error occurs while a database remote server was resolving a query on behalf of the client

Information

Related Articles