I have a working W7 XE3 application 'a2zdbtran.exe' with UNIDAC 5.3.9 using an ODBC provider connection to read tables in one database and a SQL SERVER connection to write tables in another database. It has worked perfectly using UNIDAC 5.3.9. I installed UNIDAC 5.5.11 using all the defaults and now when the statement making a table active via the ODBC connection executes this error appears:
Project a2zdbtran.exe raised exception clas EAssertionFailed with message 'Invalid fetch mode.(D:\Projects\Delphi\Dac\ODBC\Source\ODBCClasses.pas,line3074)'
I do not have a D: drive or your source code.
I uninstalled UNIDAC and re-installed the previous version 5.3 and the application runs OK as before.
What does the error message mean ?
regards
Richard Tatlow
ODBC Exception
Re: ODBC Exception
Hello,
Please specify the database you are working with via the ODBC provider, name and version of the ODBC driver, and the script for creating the table, on which the error occurs.
Please specify the database you are working with via the ODBC provider, name and version of the ODBC driver, and the script for creating the table, on which the error occurs.
Re: ODBC Exception
Hello
The ODBC driver is SYBASE SQL Anywhere 5.05.03.1666.
The database is a SYBASE SQL Anywhere database .db file.
The error can occur at run time with the statement (TUniTable)tabSrc->Open(); and at design time when I check the box TUniTable->Active.
TUniConnection connects OK.
After doing further tests I find that the error only occurs with certain tables in certain databases. There is no pattern relating to primary keys, indexes or number of records. One table that produced the error did not produce the error after I had deleted the records. The same table in a different database did not produce the error.
Perhaps the problem lies with the old SYBASE driver in WINDOWS 7.
I suggest that we leave this problem unsolved unless I can find a pattern in the errors.
Regards
Richard
The ODBC driver is SYBASE SQL Anywhere 5.05.03.1666.
The database is a SYBASE SQL Anywhere database .db file.
The error can occur at run time with the statement (TUniTable)tabSrc->Open(); and at design time when I check the box TUniTable->Active.
TUniConnection connects OK.
After doing further tests I find that the error only occurs with certain tables in certain databases. There is no pattern relating to primary keys, indexes or number of records. One table that produced the error did not produce the error after I had deleted the records. The same table in a different database did not produce the error.
Perhaps the problem lies with the old SYBASE driver in WINDOWS 7.
I suggest that we leave this problem unsolved unless I can find a pattern in the errors.
Regards
Richard
Re: ODBC Exception
Please send the script for creating and filling in the table or a database file to alexp*devart*com, in order for us to reproduce and fix the problem.