Next: Notes on specific ODBC
Up: XSB-ODBC Interface
Previous: Limitation and Guidelines for
  Contents
  Index
- ERR - DB: Connection failed
- For some reason the attempt to connect
to data source failed.
- Diagnosis: Try to see if the data source has been registered
with Microsoft ODBC Administrator, the username and
password are correct and MAXCURSORNUM is not set
to a very large number.
- ERR - DB: Parse error
- The SQL statement generated by the
Interface or the first argument to odbc_sql/1 or
odbc_sql_select/2 can not be parsed by the data
source driver.
- Diagnosis: Check the SQL statement. If our interface
generated the erroneous statement please contact us at
xsb-contact@cs.sunysb.edu.
- ERR - DB: No more cursors left
- Interface run out of non-active
cursors either because of a leak (See Section 4.3) or no
more free cursors left.
- Diagnosis: System fails always with this error. odbc_transaction(rollback) or
odbc_transaction(commit) should resolve this by freeing all cursors.
- ERR - DB: FETCH failed
- Normally this error should not occur if the
interface running properly.
- Diagnosis: Please contact us at xsb-contact@cs.sunysb.edu
Next: Notes on specific ODBC
Up: XSB-ODBC Interface
Previous: Limitation and Guidelines for
  Contents
  Index
Luis Fernando P. de Castro
2003-06-27