[unixODBC-support] truncated memo fields

tom wright tom at maladmin.com
Wed Nov 16 13:56:38 GMT 2005


Matin,
Heres the odbc_bridgec.?? file, I guess this shows the data is getting truncated.
I shall look into increasing the buffer size since I think this may be the problem. 
However please let me know if you have any other ideas.
Thanks
Tom

> Do you have a /tmp/odbc_bridgec.??? file as well you can send me?
> 
> The 5th column is (Column:5 Name:Data Type:-1 Size:2147483647 DD:0 N:1)
> but the SQLFetch is returning SQL_SUCCESS_WITH_INFO which may indicate
> a data truncated. The buffer OOB is using is what the app provided
> which was 65535 bytes.
> 
> Martin
> 
> --
> Martin J. Evans
> Easysoft Ltd, UK
> Development
-------------- next part --------------
sqlstate=01000 native=0 "[Easysoft ODBC (Server)]Warning: You are running OOB Server Multi-threaded to the MS Access ODBC driver which is not thread-safe. Switch OOB Server to MultiProcess" Column=0
sqlstate=01004 native=5 "[][Microsoft][ODBC Microsoft Access Driver]String data, right truncated on column number 5 (Data)" Column=14475272
sqlstate=01004 native=5 "[][Microsoft][ODBC Microsoft Access Driver]String data, right truncated on column number 5 (Data)" Column=14475272
sqlstate=01004 native=5 "[][Microsoft][ODBC Microsoft Access Driver]String data, right truncated on column number 5 (Data)" Column=14475272
sqlstate=01000 native=0 "[Easysoft ODBC (Server)]Warning: You are running OOB Server Multi-threaded to the MS Access ODBC driver which is not thread-safe. Switch OOB Server to MultiProcess" Column=0
sqlstate=01004 native=5 "[][Microsoft][ODBC Microsoft Access Driver]String data, right truncated on column number 5 (Data)" Column=14475272


More information about the unixODBC-support mailing list