Issue on .asp pages when using DSN for connection

Hello,
We have an asp site with content mamagement that retrieves HTML stored in
SQL Server 2000. The site works fine when a "DSN-less" connection string is
used. Due to MIS policy we need to use a system DSN, but when we connect
that way some of the pages display HTML code instead of rendering the HTML
properly.
Our DSN-less conn string which works fine:
connection="PROVIDER=SQLOLEDB;DATA
SOURCE=SQLSERVERBOX,1433;DATABASE=SQLDB1
23;USER
ID=sqluser123;PASSWORD=password123;"
Our DSN conn string which does not work properly:
connection="DSN=OUR_ASP_SITE_DSN; UID=sqluser123; PWD=password123;"
I have a feeling that the answer may be that we need to use DSN-less since
that uses the SQLOLEDB driver, instead of a DSN which uses SQL Server ODBC
(version 2000.86.1830.00). Maybe there is a way to use a DSN and the
SQLOLEDB driver?
No more hair left to pull out, any ideas out there? TIA,
~RichThe only thing I can think of is that the DSN is a user dsn not a system dsn
.
--
Russel Loski, MCSD.Net
"Richnet" wrote:

> Hello,
> We have an asp site with content mamagement that retrieves HTML stored in
> SQL Server 2000. The site works fine when a "DSN-less" connection string
is
> used. Due to MIS policy we need to use a system DSN, but when we connect
> that way some of the pages display HTML code instead of rendering the HTML
> properly.
> Our DSN-less conn string which works fine:
> connection="PROVIDER=SQLOLEDB;DATA
> SOURCE=SQLSERVERBOX,1433;DATABASE=SQLDB1
23;USER
> ID=sqluser123;PASSWORD=password123;"
> Our DSN conn string which does not work properly:
> connection="DSN=OUR_ASP_SITE_DSN; UID=sqluser123; PWD=password123;"
> I have a feeling that the answer may be that we need to use DSN-less since
> that uses the SQLOLEDB driver, instead of a DSN which uses SQL Server ODBC
> (version 2000.86.1830.00). Maybe there is a way to use a DSN and the
> SQLOLEDB driver?
> No more hair left to pull out, any ideas out there? TIA,
> ~Rich