Home > Archive > MS SQL Server ODBC > February 2006 > avoid an ODBC bug









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author avoid an ODBC bug
Imre Ament

2006-01-24, 9:23 am

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
anon

2006-02-25, 9:29 am

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
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com