Re: ADO Connection via DSN

From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 11/17/04 

Date: Tue, 16 Nov 2004 19:45:38 -0600

>I have an app that now need access to a SQL Server remote DB. Using an TADOConnection I am having problems. I used the Build Connection String dialog to build a connection and it works fine, the problem is there are parameters in the connection string that I will not know at runtime.
>All I know is the DSN Name, shouldn't this be enough? Isn't the point of connecting via a DSN so my program doesn't have to worry about login and security information? Or am I missing something?
>Thanks for any and all ideas on this one.

the DSN will get you to the server. You still need to know the database you are
connecting to and Username/password to login. Plus the access to the server can
not be blocked by a firewall. 

--
Brian Bushay (TeamB)
Bbushay@NMPLS.com

Relevant Pages

  • Re: DSN VS Logon
    ... What protocol are you connecting with? ... We're moving on servers to a new Domain then we will reimage ... Before we moved it the DSN file worked fine we ... You can check your MDAC ...
    (microsoft.public.sqlserver.security)
  • Re: oledb connectivity to SQL Server 2000
    ... you are using a login and password to create the DSN. ... Server Books Online ... >I need to create a DSN to connect to SQL Server. ...
    (microsoft.public.sqlserver.security)
  • Re: ConnectionString using DSN not working
    ... DSNs are not supported for SqlClient, ... When connecting to a SQL Server database from ... The only exception to that rule would be if you were connecting to ... And here is the one using DSN ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Sybase SQL Anywhere
    ... I would first create a DSN (ODBC datasource). ... A great method of connecting to external data is ...
    (microsoft.public.access.gettingstarted)
  • Re: ODBC connection without knowing user and password
    ... ODBC System DSN did not store password. ... As a rule, the a DBMS checks for credentials, not a DSN or the Driver ... You have not specified the DBMS you are connecting to. ...
    (microsoft.public.data.odbc)