OpenEdge Data Management: DataServer for Microsoft SQL Server

Connecting the DataServer
Connection failures and OpenEdge responses
6–28
Table 6–13 lists circumstances under which a connection might fail and describes how
OpenEdge responds.
Table 6–13: Failure responses
Failure circumstance Result
During startup The system displays an error message and returns
to the operating system prompt.
During a CONNECT statement The system aborts the remainder of the CONNECT
statement as though the remainder never existed,
and a run-time error condition occurs. Any
connections that you made prior to the failed
connection remain in effect. You can use the
NO–ERROR option with the CONNECT statement to
trap run-time errors. If you use the NO–ERROR option
and it fails, you see the same failure behavior as
you do with an unsuccessful CONNECT statement.
However, run-time error conditions do not occur.
During an attempted auto-connect The system aborts the remainder of the connect as
though the remainder never existed, and a run-time
error condition occurs. Any connections that you
made prior to the failed connection remain in
effect. You cannot trap auto-connect run-time error
conditions.
During an attempt to connect using
the Data Dictionary
During an attempt to connect a
connected MS SQL Server database
with a different logical name
During an attempt to connect a
connected MS SQL Server database
with the same logical name
During an attempt to connect an
unconnected MS SQL Server
database whose logical name is
already in use by a connected MS
SQL Server database
The Data Dictionary displays an error message and
returns to the main window.
The system responds with a run-time error
condition but you can continue. You can use the
NO–ERROR option to suppress the error.
The system responds with a warning but you can
continue. You can use the NO–ERROR option to
suppress the warning.
The system responds with a run-time error
condition and you cannot connect to the second
database.