PainMaster
New Member
I wrote in a couple days ago about ADO.NET (Scott, thanks for trying to help me!). I cannot use ADO+ member functions from the system.data.ado namespace in my asp.net pages. I have been able to use SQLClient and OLEDB, but not ADO for some reason. The first time I try to use a statement such as:"Dim myConnection As New ADOConnection"an error is thrown by the compiler. The error message reads:"BC30002: Type is not defined: 'ADOConnection'"I have tried using different ADO objects first, and the compiler still throws the same message. Any help will be greatly appreciated.
________
affair Cams (http://www.girlcamfriend.com/webcam/housewives/)I guess I'm not understanding why, exactly, you're wanting to use ADO through an ASP.NET Web page? What's wrong with ADO.NET? If you must use ADO.NET through an ASP.NET Web page, you can do:<BR><BR>Dim objConn as Object<BR>objConn = Server.CreateObject("ADODB.Connection")<BR><BR>and so forth, but you must set ASPCompat=True in your @Page directive:<BR><%@ Page ASPCompat="True" %><BR><BR>This setting forces the ASP.NET engine to access the COM component in an STA.Well, from my readings, I understand that ADO+ has has some really advanced features and that you can use them by importing the system.data.ado namespace into an aspx page. I'm just practicing, but so far, it has been the only feature of .NET that I have not been able to get working. Just wondering why...There is no such thing as ADO+. ADO.NET *used* to be called ADO+ (just like ASP.NET used to be called ASP+). Since then, though, they've changed the name to ADO.NET. So, just use the classes in the following namespaces:<BR><BR>System.Data.OleDb<BR>System.Data.SqlClient<BR><BR>Happy Programming!On Beta 1 there was a System.Data.Ado this has been renamed in Beta 2 as System.Data.OleDb<BR><BR>They are the same thing.<BR>asbA good read to learn about changes in ADO.NET from Beta1 to Beta2<BR>http://www.15seconds.com/issue/010723.htm<BR><BR>Happy Programming!
________
affair Cams (http://www.girlcamfriend.com/webcam/housewives/)I guess I'm not understanding why, exactly, you're wanting to use ADO through an ASP.NET Web page? What's wrong with ADO.NET? If you must use ADO.NET through an ASP.NET Web page, you can do:<BR><BR>Dim objConn as Object<BR>objConn = Server.CreateObject("ADODB.Connection")<BR><BR>and so forth, but you must set ASPCompat=True in your @Page directive:<BR><%@ Page ASPCompat="True" %><BR><BR>This setting forces the ASP.NET engine to access the COM component in an STA.Well, from my readings, I understand that ADO+ has has some really advanced features and that you can use them by importing the system.data.ado namespace into an aspx page. I'm just practicing, but so far, it has been the only feature of .NET that I have not been able to get working. Just wondering why...There is no such thing as ADO+. ADO.NET *used* to be called ADO+ (just like ASP.NET used to be called ASP+). Since then, though, they've changed the name to ADO.NET. So, just use the classes in the following namespaces:<BR><BR>System.Data.OleDb<BR>System.Data.SqlClient<BR><BR>Happy Programming!On Beta 1 there was a System.Data.Ado this has been renamed in Beta 2 as System.Data.OleDb<BR><BR>They are the same thing.<BR>asbA good read to learn about changes in ADO.NET from Beta1 to Beta2<BR>http://www.15seconds.com/issue/010723.htm<BR><BR>Happy Programming!