Using LV2013.
in ADODB, 'adLongVarChar' is the datatype for "TEXT" and 'adLongVarBinary' is the datatype for "BLOB".
NI_Database_API does not implement them, in the VI "vi.lib\addons\database\Auxilliary.llb\DB Tools Type and Dir to ADO.vi" it is always 'adVarChar' and 'adBinary'. This is wrong.
For some DBMS this might not be a problem, but for SQL Server this is a big problem.
If you don't specify its an adLongVarChar, SQL Server right truncate data to 8000 bytes, indeed it gives an error and drop the changes.
This error seems to be ignored due old versions of SQL Server used to support only up to 8000 bytes in a row column, but now if you specify VARBINARY(MAX) - you will need to use adLongVarBinary to use the 2TB MAX of space, or if you use TEXT (which is an alias to VARCHAR(MAX)) you will need to use adLongVarChar to use the 2TB MAX of space in row column.
I've made fixes in the NI_Database_API by myself for it to work. I feel like NI_Database_API is abandoned.
I usually don't use this API, only when I need ODBC connectivity, usually I use SQLlite for my applications.
I've found out the problem by reading this http://stackoverflow.com/questions/1074428/how-to-write-to-a-varcharmax-column-using-odbc
Attached the fix done, now inserts of long text and blobs working.
