You don't want to use a System DSN. A System DSN uses ODBC which is a
wrapper for OLE DB, meaning that you're talking about a lot of unnecessary
overhead. The .Net System.Data.SqlClient classes talk directly to the SQL
Server, without having to use OLE DB OR ODBC. Instead, you need to figure
out how to build your Connection correctly. If you post your Connection
String, perhaps we can help.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big things are made up of
lots of little things.
"Taco Bill" <no****@nospam.com.au> wrote in message
news:2d*****************@news-server.bigpond.net.au...
I am trying to do what I think is a very simple thing but I am getting
lost in the documentation.
I have a DSN set up on a server .. and I want to place a connection string
in my ASPX page so I can read from a table on the remote DB server
The DSN points to a SQL server that is using named pipes (TCP/IP would
make everything easy but its not to be)
all the doco's seem to want to use DSNless connections I have typed in so
many different connection strings but nothing brings joy.
I even found a page with so many connection strings that I felt heartened
that others also share my problems with these damn things.
Can anyone give me a snippet of code that will allow my ASPX page to use
the DSN (which by the way tests just fine)
Any tips appreciated.
Cheers Bill