Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HELP! DAta source property

Status
Not open for further replies.

emuti

MIS
Apr 18, 2001
37
US
We are building an Access to SQL Server ADP application. We have installed SQL Server 2000 not using default naming conventions. Therefore, the name of the server has ended up with what lools like the (prompted for) directory in the path (CAL_SQL\DDSQLSERVER). Thus, the Data Source property needs be "CAL_SQL\DDSQLSERVER". But because there is an embedded slash, the Data Source Property of the ADO Connection never recognizes the full name of the server when the full name is assigned it, and instead, interprets the name assigned up to the slash (In this example, the Data Source will display as "CAL_SQL"). This is forcing the user to continually select the datasource (Server) list box on Login, rather than me supplying it in the connectionstring. How can I force acceptance of the proper full name of the server by this driver (SQLOLEDB ver 2.6)?
 
Multiple instances of SQL Server 2000 can be installed on a server so you will likely see more naming like you describe. Open the Client Network Utility on the client machine and give the instance of SQL Server an alias like "CA_CAL". Check the port that the instance of SQL Server listens on and make sure the client setup matches. Terry
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top