Until now I used OleDB but in recent news Microsoft says it will be deprecated.
So we must go back to ODBC?
Does anyone have tips on this?
Microsoft dropped OLEDB support in the SQLServer Native client already.
If you want to keep using OLEDB from TeamDeveloper to a SQLServer 2014 or 2016 instance, you will need to install the Microsoft SQL Server Native Client 2012.
Both SQL Server 2014 and 2016 are compatible to the SQLServer 2012 Native client.
If your source implements SqlCreateSession/SqlCreateStatement/SqlCommitSession, it would be wise to start changing your code to just using SqlConnect.
Lelystad - The Netherlands
I connect to all versions of SqlServer with all versions of TD with this in the ODBC session of sql.ini:
Is there any change - don't see anything in the documents.
ODBC connection for SQL Server (SQLSRV32.ALL) works well on all SQL Server versions ( From SQLServer 7.0 to SQLServer 2016)
After changing the ODBC to SqlServer native Client (SQLNCI10.DLL) , my application running on Team developer 2 & Team developer 5 does not work.
Error Message [Microsoft][SQL Server Native Client 11.0]Invalid character value for cast specification
It affects fields DATE/TIME. example: UPDATE ACCESS.dbo.SYSUSR SET LSTLOGIN= :dlbpwd.dtDate WHERE USRCOD = :p_sUsrcod
(dlbpwd.dtDate) is defined as DATE/TIME.
Can I have a solution for this.
BTW, for TD, the remotedbname is not needed. This is what CCOD.pdf says:
Notes: The remotedbname parameter is not necessary for applications built using Team Developer. It is required if you want to use the SqlTalk utility to connect to the ODBC data source.
When connecting to any ODBC data source where the data source name was configured by the ODBC Administrator tool, your application can bypass the remotedbname parameter altogether, and set the variable SqlDatabase to the actual ODBC data source name. Using the above example, if you issue the following statements (assume SqlUser and SqlPassword are set), your program will connect correctly to the Microsoft SqlServer 7.0 data source without using the remotedbname parameter in SQL.INI:
Set SqlDatabase = "MS SqlServer 7.0"
Call SqlConnect (hSql)
Attempt to fetch non-numeric data into numeric column
As and when it feels like it this happens:
Sometimes Input buffer too small.
Just cannot proceed.
I am testing right now against TD6 and TD7 - so far Ok.
The variable SqlUDL in place of SqlUser, SqlDatabase and SqlPassword can contain a .udl file name with the SqlServer connection string in it, or the string itself. A .udl file is easiest, just create a .txt file, rename it to .udl , double click the .udl file, and a connection wizard allows easy configuration.
Go here for details / download: https://blogs.msdn.microsoft.com/sqlnat ... ql-server/
Go here for my sample: https://forum.tdcommunity.net/viewtopic.php?f=6&t=45816
Bankside Systems Ltd. ( New Zealand )
Happy to inform that testing with 5.2 and 7.x and is working well without any change on generated EXE.
The rule is always the same: do not believe too quickly what they say .... wait .... wait ... still a little ...
Who is online
Users browsing this forum: [Ccbot] and 0 guests