ODBC DataSource name problem

Hi All
We have an application which is used the ODBC Data Source to comunicate
with the database. So during the installation of the product the
installation creating
the database name like : VAPost and server = datasource name which is 'VAPos
t'
not the real server name in the Microsoft SQL server DSN Configuration optio
n.
Also the installation is created the Alias in SQL Server Client Network
Utility for
'VAPost' which has Server alias = 'VAPost', NetWork library = 'TCP/IP' and
the Connection parameters is the ip address of the server.
So my application is used the DSN name 'VAPost' to connect to the database b
ut
there is an error message regarding "Communication Link Failure". I could
not figure out where is the problem but the same configuration it works on
other server. Any help is greatly appreciated.
Thanks,
JodieHi Jodie,
You are using a system DSN? You should access that DSN using a ".Net
Providers\ODBC data providers" Connection. Configure it to use the DSN.
Then within the dataflow, create a DataReader data source. Set it to use th
e
DSN connection. You control what is being pulled by the SQLCommand on the
second tab.
-Steven
"Jodie" wrote:

> Hi All
> We have an application which is used the ODBC Data Source to comunicate
> with the database. So during the installation of the product the
> installation creating
> the database name like : VAPost and server = datasource name which is 'VAP
ost'
> not the real server name in the Microsoft SQL server DSN Configuration opt
ion.
> Also the installation is created the Alias in SQL Server Client Network
> Utility for
> 'VAPost' which has Server alias = 'VAPost', NetWork library = 'TCP/IP' and
> the Connection parameters is the ip address of the server.
> So my application is used the DSN name 'VAPost' to connect to the database
but
> there is an error message regarding "Communication Link Failure". I could
> not figure out where is the problem but the same configuration it works on
> other server. Any help is greatly appreciated.
> Thanks,
> Jodie
>