The EDS environment can be in one of four states:

The following table lists the next valid state for each core command when called from a given state. InvHndl indicates an INVALID_HANDLE return code.

 

The following table lists the next valid state for each extended command when called from a given state. InvHndl indicates an INVALID_HANDLE return code.

 

1Allocation functions should never be called for already-allocated handles, as the driver will lose any information associated with the handle and the handle will return to the allocated state (S1).

2EDSDisconnect returns a SQLSTATE of 25000 (Invalid transaction state) only if there is an incomplete transaction associated with the HDBC.

3The HDBC is not in a connected state until EDSBrowseConnect returns EDS_SUCCESS or EDS_SUCCESS_WITH_INFO. Until then, EDSBrowseConnect; may be called repeatedly on the HDBC. However, calling EDSConnect or EDSDriverConnect on an HDBC that is being browsed will return an SQLSTATE of 08002 (Connection in use).

4Transition for information option EDS_ODBC_VER, which can be returned by the Driver Manager. Otherwise, the Driver Manager returns EDS_ERROR with an SQLSTATE of 08003 (Connection not open).