Display next result in a recordset

Question

Hi everyone,
I'm building an ASP page (working with MS Access and DWCS3)
and want to use the top three results from a query as dynamic
elements of my page but I need to be able to work with the 1st, 2nd
and 3rd items in the recordset separately.
The records in my table have an autonumber primary key. If
that's all I was working with, I'd create three recordsets using
MAX ID, MAX ID -1, and MAX ID - 2. However, I need to use a filter
condition that won't let me do that. My resulting IDs might be 12,
5 and 2, for instance.
Any suggestions?
Regards,
--NewDevGuy

Answer 1

NewDevGuy wrote:
> Awesome. I was able to make this work. Thanks very much
for the help. In
> hindsight, I see now that I've been using complex SQL
and multiple recordsets
> to manipulate data when a VB script command (which I
only know through building
> sites with DW), as in this case, would be a better
solution.
>
> Now that I've gotten this to work, I now have a new
wrinkle to figure out. I
> want to apply a 'show region if'-type behavior depending
on the value in a
> column. Let's say the values are "0" and "-1" (based on
a checkbox from a
> form). The 'show region if' behaviors built into DW are
based on recordsets.
> Now that I'm only working with one recordset, I'm not
sure how to do this.
>
> If you have any tips on how I can show "A" if the column
value is 0 or "B" if
> the column value is -1, I'll be doubly grateful.
There are a couple ways to approach this, both are simple.
1. Advanced Conditional Region Extension:
http://www.dmxzone.com/ShowDetail.asp?NewsId=553
2. Drag your recordset binding onto the page, it will look
like this:
<%= rsRecordSet.Fields.Item("YourColumn").Value %>
Change it to:
<% If rsRecordSet.Fields.Item("YourColumn").Value = 0 Then
%>A<% End if %>
<% If rsRecordSet.Fields.Item("YourColumn").Value = -1
Then %>B<% End if %>
3. Do it in your SQL using a CASE statement, here is a
simplified version:
SELECT CASE YourColumn WHEN 0 THEN A WHEN -1 THEN B END AS
YourNewColumn
FROM YourTable
I always go for the SQL route, its tidier, and fairly easy
once you
understand CASE. I am assuming that you are using Access,
which I am not
sure if it supports CASE.
Dooza
Posting Guidelines
http://www.adobe.com/support/forums/guidelines.html
How To Ask Smart Questions
http://www.catb.org/esr/faqs/smart-questions.html