I have not found any way to force SQL type compatibility, but I have
worked around it by using CAST/CONVERT in the SQL statement to make
UniData see the data as a type it did recognize. In my case it was a
matter of BigInt not being handled (which is ironic, since U2 doesn't
usually fuss about whether something is a string or a number). I don't
know if that is going to work for your situation, though.
HTH,
David Beahm
Date: Fri, 13 Jul 2007 05:43:44 -0600
From: "Trey Miller" <[EMAIL PROTECTED]>
Subject: [U2] BCI Interface
Hello,
I'm on a system running UniData 6.0.
I'm attempting to use the BCI to return an SQL table from a 2003 MsSql
server. I've established a connection and can execute the SQLExecDirect
with a "select * from <tablename>" against several tables with no issue, but
any table which includes a binary column fails with an unsupported data type
error. The documentation shows that there are provisions for binding
SQL.B.BINARY data types when pushing data out of UniData and onto the data
source. I'm wondering if there are any provisions for binding to a binary
data column when attempting to bring an entire table into UniData through
the BCI. I can not seem to find any.
Thanks in advance!
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
