A little problem which I can't seem to resolve. I'm using ADODB to loop out values from a database.

My connection is simple:

ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\mydb.mdb"
Connection.Open(ConnectionString)

Command.ActiveConnection = Connection.Open

Once the connection has been made I want to loop out the information contained in the table called "Surf"

Command.CommandText = "SELECT * FROM Surf"
Command.CommandTimeout = 10
Command.CommandType = ADODB.CommandTypeEnum.adCmdText

SQLString = Command.Execute

Now here is my problem:

In ASP it was fairly simple to loop out the required information by specifying which record in the table I want to display by doing the following:

variable1 = SQLString("Recordname")

and it would give me the correct value, but I'm trying to use the same type of connection in ASP.NET and keep on getting an error such as: "Value of type 'ADODB.Field' cannot be converted to 'String'".

Am I doing something wrong or is there a specific method I should use?

Any help would be appreciated

I woulld fill a data set with the results from your query. Then loop through the dataset, getting each column in the table you need, and assign it to your respective variables.

Eric,

Why are you attempting to use ADODB in ASP.NET? Perhaps you need to read up a little on the new classes available in ADO.NET. There are classes for connecting to and retrieving data from various data sources such as the SqlConnection, SqlDataReader and SqlDataAdapter (for Access/JET you can use the OleDb flavor of these classes). Also there are several classes that are data-store agnostic that you can use to work with data in .NET such as DataTable and DataSet.

-Peter

The reason for using adodb is because i developed the previous version with asp and i used adodb to connect. this worked perfectly, but seeing that i want to upgrade to the new .net standard i would like to keep my current connection as is. i will in due course update the entire app but for now only want to use what i have been doing so far.

But thanks for you help the correct method was specify the .value of the field i'm trying to loop out.

Isn't this a paradoxical statement? You're likely to run into more problems using ADODB in .NET then if you just move to ADO.NET (as you have found already). There isn't much to it. Indeed the ADO.NET objects (*DataReader, DataSet, DataTable) are much easier and more intuitive than the archaic RecordSet object.

I'm willing to bet that if you take a little time to learn about the new classes in ADO.NET your application conversion time and effort will be reduced. But that's up to you.

-Peter

I already know the language, but to make things easier for my students I like to grind them with what used to be, the old language. That way they actually understand why the new language came to be.

Thank you for your input on this matter, I must agree that switching to ADO.Net makes life must easier.

Eric,

I hope your students drop your class and find another teacher that wants to teach them how things SHOULD be done- rather than filling their heads with the wrong way to do things first.

There is no value in "grind" them with the old way when the old way sucks.

Do the Industry a favor and teach them how to do it right- I see way too many people doing it the wrong way, and now I know why.


Hal Levy
I am here to help you, not do it for you.
That is, unless you hire me. I am looking for work.