Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SQL 2000 Connection
Message
From
03/12/2001 18:56:37
Anirban Saha
Mindteck Consulting Inc.
Iselin, New Jersey, United States
 
 
To
All
General information
Forum:
Visual Basic
Category:
SQL Server
Title:
SQL 2000 Connection
Miscellaneous
Thread ID:
00589011
Message ID:
00589011
Views:
49
Hi,

Currently I'm working with a system. System is developed in VB 6.0. Database is SQL 2000 Failover Cluster Server. I'm using OleDB to connect the SQL 2000. As you know MDAC 2.6 comming with SQL 2000 by default. Due to some reason I have to use MDAC 2.5 SP1. Although in my workstation I have Mdac 2.6. But the user of my application will get only MDAC 2.5 SP1 ( according to my company rule ). There is no workstation currently available with exact User's configuration where I can test My application. I have been told that My application is not able to connect to SQL 2000 through OLEDB. By once the technical Service people created a system DSN for SQL 2000 on the user's PC, application started working. It's really giving me a hard time to beleive that solution.

Here is the syntax I have used for OLEDB:

"Provider=SQLOLEDB.1;SERVER=NPTSQLP,1689;DATABASE=ivrdata; UID=ivrsql; PWD=ivrpwd"

You can see that I have put "NPTSQLP,1689" as a Server.

Because my Database is SQL 2000 Fail Over Cluster Server. According to the Technical Support group MDAC 2.5 SP1 does not work with the Server Name. It's only Works with Server Instance and Port Name.

The name of my Server is : NPTSQLP\MSSQLP
Instance of my Server id NPTSQLP and Port Number is 1689.


FYI : MDAC 2.6 works with the Server Name. You can be able to work with Server Name "NPTSQLP\MSSQLP".


My Question is what I have been told is right ? Is there any explanation for this ? I would appreciate if some one can help me out of this.

Thanks,

Anirban Saha
Reply
Map
View

Click here to load this message in the networking platform