I am connecting to a SQL Anywhere 17 database using the oledb provider SAOLEDB. I am using vb.net (2005) and can create a connection, read, write and execute stored procedures. But it seems that there are some issues with some of the datatypes being retrieved.
We have upgraded SQL Anywhere from 10 to 17 and have started getting these errors.
I appreciate that dotnet 2005 is old, have these datatypes changed? Apart from CAST or turning off CONVERSION_ERROR is there anything else I might be able to do?
asked 06 Dec '16, 11:35
For time and timestamp with time zone data types, try using the "Delphi=Yes" connection parameter. Newer versions of the provider implement time and timestamp with time zone using modern types like DBTYPE_DBTIME2 and DBTYPE_DBTIMESTAMPOFFSET. See http://dcx.sap.com/index.html#sqla170/en/html/3bd9b5276c5f101494da9a0931d44c40.html.
Not sure what the GUID issue is all about.
I tried executing "select newid()" using a test script and it worked fine. Did not need to use any special options.
answered 07 Dec '16, 09:54