I have a recordset which uses two columns as variables, 'type' and 'date'. I
have a form which posts to the same page it is on with two list boxes, one
for the type and another for the dates BETWEEN which the information needs
to fall.
Everything works great except when I use next/previous navigation. When I
try to use Next I go to the original recordset. (the default one, not the
one filtered from the form)

I've seen the posts about using Request instead of Request.Form so I've done
that.

I think my problem comes since I am using two columns to filter the
recordset. When UD uses the <%=MM_moveNext%> code it only adds the 'type'
variable and the offset, not the date variable. So I added this
<%=MM_moveNext%>&d=<%= Server.URLEncode( Request("d" ) %>. When I do this I
get the sorted recordset when I try to go to Next.

Anyone have any help for me? What am I missing here?

Some info -----
The Filter part of the query
HAVING (((event.ev_startdate) BETWEEN qFilterDate) AND ((event.ev_type)
LIKE 'qFilterType')

Variables
name: qFilterDate
default value: %
runtime: request("d"

name: qFilterType
default value: Date() AND Date()
runtime: request("t"

Url variables
<%=MM_moveNext%>
activities.asp?t=%25&offset=8

w/ <%= Server.URLEncode( Request("d" ) %>
activities.asp?t=%25&offset=8&d=%235%2F22%2F91%23+AND+%235%2F22%2F11%23