Dynamic operator used in a search/results page

[Elliott]

Hi,
I have a search results page running where I want the user to filter the
results based on a date expression, they can select GREATER THAN, LESS THAN
or EQUAL TO from a drop down list (where the values are '>','<' and '=') and
then enter the year in a seperate text field next to the list. The user then
submits the search and the list of results are then displayed on the
following page.

What would be the best way to get this to work? I already have a recordset
on the results page to compare other field entries with the database items
(such as model type, description and colour). Since the recordset requires
me to use an operator, I don't know how to get dreamweaver to recognise the
dynamic operator parameter as the operator to use in the recordset!

Any ideas??

P.S Since the date is just the year, eg 1995, it does not need to be set as
a date field, it can be set to a number or text field.

Thanks

Tom

[Julian Roberts]

It'd work in the same way as your search. ie. You'd have SQL like

select * from t where d mmcolparam1 mmcolparam2

so, the mmcolparam1 would be replaced by the dynamic operator.

--

Jules
[url]http://www.charon.co.uk[/url]

Charon Cart 3
[url]http://www.charon.co.uk/charoncart[/url]

ICQ 51328805



Elliott wrote:

> Hi,
> I have a search results page running where I want the user to filter
> the results based on a date expression, they can select GREATER THAN,
> LESS THAN or EQUAL TO from a drop down list (where the values are
> '>','<' and '=') and then enter the year in a seperate text field
> next to the list. The user then submits the search and the list of
> results are then displayed on the following page.
>
> What would be the best way to get this to work? I already have a
> recordset on the results page to compare other field entries with the
> database items (such as model type, description and colour). Since
> the recordset requires me to use an operator, I don't know how to get
> dreamweaver to recognise the dynamic operator parameter as the
> operator to use in the recordset!
>
> Any ideas??
>
> P.S Since the date is just the year, eg 1995, it does not need to be
> set as a date field, it can be set to a number or text field.
>
> Thanks
>
> Tom

[Elliott]

You would have thought that would work but it doesn't, dreamweaver (and the
previewed ASP page) still says "invalid syntax (missing operator) in query
expression..." because it does'nt recognise the mmcolparam1 parameter as a
valid substitution for an operator.

Am i missing something else?

Cheers

Tom

[url]www.telliott.co.uk[/url]

"Julian Roberts" <newsgroup@charon.co.uk> wrote in message
news:beu1cv$de1$1@forums.macromedia.com...

> It'd work in the same way as your search. ie. You'd have SQL like
>
> select * from t where d mmcolparam1 mmcolparam2
>
> so, the mmcolparam1 would be replaced by the dynamic operator.
>
> --
>
> Jules
> [url]http://www.charon.co.uk[/url]
>
> Charon Cart 3
> [url]http://www.charon.co.uk/charoncart[/url]
>
> ICQ 51328805
>
>
>
> Elliott wrote:

> > Hi,
> > I have a search results page running where I want the user to filter
> > the results based on a date expression, they can select GREATER THAN,
> > LESS THAN or EQUAL TO from a drop down list (where the values are
> > '>','<' and '=') and then enter the year in a seperate text field
> > next to the list. The user then submits the search and the list of
> > results are then displayed on the following page.
> >
> > What would be the best way to get this to work? I already have a
> > recordset on the results page to compare other field entries with the
> > database items (such as model type, description and colour). Since
> > the recordset requires me to use an operator, I don't know how to get
> > dreamweaver to recognise the dynamic operator parameter as the
> > operator to use in the recordset!
> >
> > Any ideas??
> >
> > P.S Since the date is just the year, eg 1995, it does not need to be
> > set as a date field, it can be set to a number or text field.
> >
> > Thanks
> >
> > Tom

>
>

[Julian Roberts]

What have you use as the Default for the parameter. Or it could well be a
problem with something else in the SQL statement. To troubleshoot, use this
just before opening the recordset

Response.Write recordsetname.Cource
Response.End

--

Jules
[url]http://www.charon.co.uk[/url]

Charon Cart 3
[url]http://www.charon.co.uk/charoncart[/url]

ICQ 51328805



Elliott wrote:

> You would have thought that would work but it doesn't, dreamweaver
> (and the previewed ASP page) still says "invalid syntax (missing
> operator) in query expression..." because it does'nt recognise the
> mmcolparam1 parameter as a valid substitution for an operator.
>
> Am i missing something else?
>
> Cheers
>
> Tom
>
> [url]www.telliott.co.uk[/url]
>
> "Julian Roberts" <newsgroup@charon.co.uk> wrote in message
> news:beu1cv$de1$1@forums.macromedia.com...

>> It'd work in the same way as your search. ie. You'd have SQL like
>>
>> select * from t where d mmcolparam1 mmcolparam2
>>
>> so, the mmcolparam1 would be replaced by the dynamic operator.
>>
>> --
>>
>> Jules
>> [url]http://www.charon.co.uk[/url]
>>
>> Charon Cart 3
>> [url]http://www.charon.co.uk/charoncart[/url]
>>
>> ICQ 51328805
>>
>>
>>
>> Elliott wrote:

>>> Hi,
>>> I have a search results page running where I want the user to filter
>>> the results based on a date expression, they can select GREATER
>>> THAN, LESS THAN or EQUAL TO from a drop down list (where the values
>>> are '>','<' and '=') and then enter the year in a seperate text
>>> field
>>> next to the list. The user then submits the search and the list of
>>> results are then displayed on the following page.
>>>
>>> What would be the best way to get this to work? I already have a
>>> recordset on the results page to compare other field entries with
>>> the database items (such as model type, description and colour).
>>> Since
>>> the recordset requires me to use an operator, I don't know how to
>>> get dreamweaver to recognise the dynamic operator parameter as the
>>> operator to use in the recordset!
>>>
>>> Any ideas??
>>>
>>> P.S Since the date is just the year, eg 1995, it does not need to be
>>> set as a date field, it can be set to a number or text field.
>>>
>>> Thanks
>>>
>>> Tom