, but as soon as i loaded SQL SERVER 2005 it will not pick up the DB or Source path.......I configured the 2005 DB to Except Remote connection vi TCP/IP with no luck, I also attempted to create a ODBC connection via Native Client which returns an error stating that the connection failure may be due to the fact that SQL SERVER doesn`t by default allow remote connections......any advise would be highly appreciatedTrouble Connecting To SQL SERVER 2005
-
floris olivier
- Posts: 1
- Joined: Fri 27 Jan 2006 07:44
Trouble Connecting To SQL SERVER 2005
I am in the proccess of installing a Borland cpp 6.0 windows app on a Small Bussiness Server 2003.....I initally used SQl SERVER 2000 for developement which worked fine connecting it with the ADOConnection Data Control as well as the the CLab SQL SERVER data control , but as soon as i loaded SQL SERVER 2005 it will not pick up the DB or Source path.......I configured the 2005 DB to Except Remote connection vi TCP/IP with no luck, I also attempted to create a ODBC connection via Native Client which returns an error stating that the connection failure may be due to the fact that SQL SERVER doesn`t by default allow remote connections......any advise would be highly appreciated
, but as soon as i loaded SQL SERVER 2005 it will not pick up the DB or Source path.......I configured the 2005 DB to Except Remote connection vi TCP/IP with no luck, I also attempted to create a ODBC connection via Native Client which returns an error stating that the connection failure may be due to the fact that SQL SERVER doesn`t by default allow remote connections......any advise would be highly appreciatedMake sure that:
1. Microsoft SQL Native Client major version is 9.
2. SQL Server network protocols configured properly. To get more information see "Configuring Server Network Protocols and Net-Libraries" in SQL Server 2005 Books Online.
3. Try to fill TMSConnection.Options.NetworkLibrary property according to used network protocol.
1. Microsoft SQL Native Client major version is 9.
2. SQL Server network protocols configured properly. To get more information see "Configuring Server Network Protocols and Net-Libraries" in SQL Server 2005 Books Online.
3. Try to fill TMSConnection.Options.NetworkLibrary property according to used network protocol.