Welcome to Team Developer Community Forum. A place created by the community, for the community !
This is a resource for Q & A and discussion about everything related to OpenText Gupta Team Developer, SqlBase, TD Mobile and Report Builder.
It is the alternative for the OpenText customer forums which can only be accessed with an active support contract.
Please register your account now. It will make you part of the active community.
Also, this guest message will not be displayed for registered users.
As a bonus, registered users have access to the 'Newsgroups' subforum, holding 10 years worth of posts from the good old Gupta newsgroups.
Having an account gives you the opportunity to ask questions and get help from others.
We hope this free gathering will help you and the community getting forward!
The forum site admins.
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?
- Site Admin
- Posts: 6
- Joined: 07 Mar 2017, 08:46
- Location: Lelystad, The Netherlands
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
Who is online
Users browsing this forum: No registered users and 1 guest