Kbase 16806: CONNECT NO-ERROR Not Trap Certain Errors Connect Remote DB
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
CONNECT NO-ERROR Not Trap Certain Errors Connect Remote DB
When connecting to a remote database from the 4gl with the
CONNECT statement with NO-ERROR option, certain errors will
not be surpressed.
Errors that will not be surpressed are errors that raise a STOP
condition. For example, attempting to connect to a database called
test with the following:
CONNECT testr -H tsibm1 -S demosv1 -N TCP NO-ERROR
will give the following errors even though the connect statement
has the no-error option:
Disconnected from server because database name was incorrect. (437)
** Server rejected login. (700)
What has happened is that a connection was made to the database
server with the service but the database name was incorrect which
then caused a disconnection. Losing a database connection raises
the STOP condition, therefore, the errors are not trapped and
surpressed with no-error.
References to Written Documentation:
Progress Version 8 Programming Handbook
Progress Software Technical Support Note # 16806