"The proposed join does not form a clearly connected list. (table '%2') %1"
| Item | Description |
|---|---|
|
SQLCode |
-1000023L |
|
Constant |
EMSG_CAT_JINDEXCLEAR |
|
SQLState |
QDA23 |
|
ODBC 2 State |
ERROR |
|
ODBC 3 State |
ERROR |
|
Sybase Error Code |
20683 |
|
Severity Code |
|
|
Parameter 1 |
location of the exception |
|
Parameter 2 |
The name of the base table that caused the error.. |
Join Indexes can be entered in one of two ways. Using the order of the tables in the SQL statement or using primary<->foreign keys. When using the order method the order determines the relationships between the tables. The order is from a one to many or one to one. It is possible to ask for a join Index that can not be constructed. This error could be from one of the following: 1) The same table is specified twice. 2) The relationships of one to one/many are not consistent with the indexes defined. 3) A table specified has no relation to the tables previously encountered in the syntax. For example: A FULL OUTER JOIN B FULL OUTER JOIN C FULL OUTER JOIN D In this example C has no relation (fields in common) to A or B. The user intended C to Join with D. Some joins can not be defined using the ANSI syntax which depends on order to determine the one to one/many relationship. It is recommended to use the primary and foreign keys syntax to avoid any join definition problems.