DSN Connection Issue

Inside a classic ASP web application there is only one generic function to
connect to the database. This was verified by commenting the connection
string out and watching the application fail. Provided in the connection
string is the provider, DSN, username, and password. A Valid DSN was verified
on the server that points to a SQL 2005 database. Renaming the DSN or even
completely removing the DSN is still linking the old 2000 database. What else
could possibly link the connection string to the old server?



--
Regards,
Shaun Goldston

Liberalism is treason!
Vote Republican

Re: DSN Connection Issue

"A_Republican" wrote in message
news:A5BB0F37-7849-4702-A1BB-156A6BF17507@microsoft.com...
> Inside a classic ASP web application there is only one generic function to
> connect to the database. This was verified by commenting the connection
> string out and watching the application fail. Provided in the connection
> string is the provider, DSN, username, and password. A Valid DSN was
> verified
> on the server that points to a SQL 2005 database. Renaming the DSN or even
> completely removing the DSN is still linking the old 2000 database. What
> else
> could possibly link the connection string to the old server?


I started to offer a possible solution, but I was so distracted at your sig
that I digressed.
Please take the politics elsewhere.

LM

Re: DSN Connection Issue

>> Please take the politics elsewhere.

Why? You didn't.

Bob Lehmann

"Larry Miley" wrote in message
news:%23$LCtIW%23GHA.4428@TK2MSFTNGP04.phx.gbl...
>
> "A_Republican" wrote in message
> news:A5BB0F37-7849-4702-A1BB-156A6BF17507@microsoft.com...
> > Inside a classic ASP web application there is only one generic function
to
> > connect to the database. This was verified by commenting the connection
> > string out and watching the application fail. Provided in the connection
> > string is the provider, DSN, username, and password. A Valid DSN was
> > verified
> > on the server that points to a SQL 2005 database. Renaming the DSN or
even
> > completely removing the DSN is still linking the old 2000 database. What
> > else
> > could possibly link the connection string to the old server?
>
>
> I started to offer a possible solution, but I was so distracted at your
sig
> that I digressed.
> Please take the politics elsewhere.
>
> LM
>
>

Re: DSN Connection Issue

When you think about it logically, anyone that puts ANY lable on themselves
other than "Independant" is a complete and total moron. Why would you call
yourself a democrat? or a republican? or a liberal? or conservative? Does
this mean you MUST now agree with your party? Well what if you dont? If you
dont, then youre NOT what you just labeled yourself. So why no be an
"independant thinker" and make up YOUR mind on an issue-by-issue basis?

morons...




"Bob Lehmann" wrote in message
news:uEdN8SW%23GHA.4712@TK2MSFTNGP03.phx.gbl...
>>> Please take the politics elsewhere.
>
> Why? You didn't.
>
> Bob Lehmann
>
> "Larry Miley" wrote in message
> news:%23$LCtIW%23GHA.4428@TK2MSFTNGP04.phx.gbl...
>>
>> "A_Republican" wrote in message
>> news:A5BB0F37-7849-4702-A1BB-156A6BF17507@microsoft.com...
>> > Inside a classic ASP web application there is only one generic function
> to
>> > connect to the database. This was verified by commenting the connection
>> > string out and watching the application fail. Provided in the
>> > connection
>> > string is the provider, DSN, username, and password. A Valid DSN was
>> > verified
>> > on the server that points to a SQL 2005 database. Renaming the DSN or
> even
>> > completely removing the DSN is still linking the old 2000 database.
>> > What
>> > else
>> > could possibly link the connection string to the old server?
>>
>>
>> I started to offer a possible solution, but I was so distracted at your
> sig
>> that I digressed.
>> Please take the politics elsewhere.
>>
>> LM
>>
>>
>
>