Recordset is another created/instanciated Object. It is a collection of data taken from a database. Recordset has 26 properties, 25 methods, 11 events, and two (2) collections. The vast majority of Recordset is beyond the scope of this web site.
The database we are using for lesson 16 and lesson 17 is an MS Access 2000 file (not the best database for large sites). The file is called htmlColor.mdb and it has a single Table called colorChart. The database Table has three columns and they are called ID, colorName, and hexValue.
The illustration below shows how we will cycle through these records.
In this example we cycle through the records row by row. We will use the MoveNext() Method to go from record #1 to #2, etc. Then, we will access specific data in each row by using the column name.
Below is the script for Lesson 17. It's exactly the same as the script for lesson 16. The difference is that we will focus on those lines of code that deal with Recordsets.
Click Here to run the script in a new window.
We'll dissect the Recordset statements from top to bottom. In this case that means starting with the Dynamic Link Library.
<!-- METADATA TYPE="typelib" FILE="C:\Program Files\Common Files\System\ado\msado15.dll" -->
What in the world is a DLL? A Dynamic Link Library holds values without tying up memory. Here's how it works. If you try to use a variable that is undefined, ASP will first look it up in the DLL. You'll notice in the
Managing the Recordset:
First we must instanciate a Recordset, which we do in the little snippet below.
var RS = Server.CreateObject("ADODB.Recordset");
Next we create a Text Command. The text in question comes in the form of S.Q.L. (Structured Query Language). SQL is beyond the scope of this web site, but the command below means select ID, colorName and hexValue from the colorChart Table.
var sql="SELECT ID, colorName, hexValue FROM colorChart;";
Then we open the Recordset. The five arguments in order are: source, connection, cursor type, lock type, and options .
Using a loop, we tell ASP to do certain things for as long as we haven't hit EOF, which means End of File.
Next, we access specific collums in the Recordset by name.
Response.Write( RS("hexValue") + "\">" + RS("colorName") );
Then we move down from one row of records to the next.
Finally, when we reach EOF, the loop relinquishes control and we can close the Recordset Object.
The Rest of The Story:
This is by no means a complete lesson on Recordsets; it wasn't meant to be. The rest of the story on Recordsets is out there, on the internet, and in books. There is one other thing we have to talk about with Recordsets. We do that in lesson 18.