Hi!
I have to manage a program what can copy data from MS Access to SQL server
(2000 and 2005).
I work with C++ and DAO 3.6.
I have a bug from the SQL server ODBC driver : "Invalid locator
de-referenced" during copy BLOB columns.
The columns bigger than 250K (I found Article ID : 245714).
I do not want to set the ODBC driver to 6.5 compatibility mode (I am afraid
other bugs will appear on the other parts of my program).
I try to update columns one by one with SQL UPDATE command but receive an
E_DAO_OutOfMemory (about 500 kbyte SQL statment).
Can anyone help me to avoid this bug (for example install specified MDAC
version)?
Regards,
ImreI managed to avoid this bug by passing SQL_LEN_DATA_AT_EXEC(250000) as the
nullindicator to SQLBindParameter and then put the data in 250000 byte
chunks
Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts
Sunday, February 19, 2012
avoid an ODBC bug
Hi!
I have to manage a program what can copy data from MS Access to SQL server
(2000 and 2005).
I work with C++ and DAO 3.6.
I have a bug from the SQL server ODBC driver : "Invalid locator
de-referenced" during copy BLOB columns.
The columns bigger than 250K (I found Article ID : 245714).
I do not want to set the ODBC driver to 6.5 compatibility mode (I am afraid
other bugs will appear on the other parts of my program).
I try to update columns one by one with SQL UPDATE command but receive an
E_DAO_OutOfMemory (about 500 kbyte SQL statment).
Can anyone help me to avoid this bug (for example install specified MDAC
version)?
Regards,
Imre
I managed to avoid this bug by passing SQL_LEN_DATA_AT_EXEC(250000) as the
nullindicator to SQLBindParameter and then put the data in 250000 byte
chunks
I have to manage a program what can copy data from MS Access to SQL server
(2000 and 2005).
I work with C++ and DAO 3.6.
I have a bug from the SQL server ODBC driver : "Invalid locator
de-referenced" during copy BLOB columns.
The columns bigger than 250K (I found Article ID : 245714).
I do not want to set the ODBC driver to 6.5 compatibility mode (I am afraid
other bugs will appear on the other parts of my program).
I try to update columns one by one with SQL UPDATE command but receive an
E_DAO_OutOfMemory (about 500 kbyte SQL statment).
Can anyone help me to avoid this bug (for example install specified MDAC
version)?
Regards,
Imre
I managed to avoid this bug by passing SQL_LEN_DATA_AT_EXEC(250000) as the
nullindicator to SQLBindParameter and then put the data in 250000 byte
chunks
Subscribe to:
Posts (Atom)