Joe,
"ADODB.Connection" is classic ADO which you would normally use only with
classic ASP and VBScript. Is there any particular reason why you need to do
this instead of using the ADO.NET managed providers?
Is this some sort of a converted project from Classic ASP?
Peter

Signature
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
> I'm getting the following error in my application:
>
[quoted text clipped - 21 lines]
> ------->>>>>>http://www.NewsDemon.com<<<<<<------
> Unlimited Access, Anonymous Accounts, Uncensored Broadband Access
Joe Befumo - 19 Feb 2006 21:21 GMT
Yeah, it was. I ultimately got it working, then learned about the better way
of doing things in Dot.Net, so I converted, successfully. Thanks.
Joe
> Joe,
> "ADODB.Connection" is classic ADO which you would normally use only with
[quoted text clipped - 32 lines]
>> ------->>>>>>http://www.NewsDemon.com<<<<<<------
>> Unlimited Access, Anonymous Accounts, Uncensored Broadband Access
Joe,
While it may not make supersense this moment, ADODB has been utterly
abandoned in DotNet.
The only time one might use them, is to talk to some legacy code.
The "new kids on the block" are the
DataSet
IDataReader
Do a google for DataSet IDataReader ADODB and read up.
Here is a decent one.
http://www.simple-talk.com/2005/06/10/adonet-data-access/
> I'm getting the following error in my application:
>
[quoted text clipped - 21 lines]
> ------->>>>>>http://www.NewsDemon.com<<<<<<------
> Unlimited Access, Anonymous Accounts, Uncensored Broadband Access