Well, I built a search form with date range controls on it, and it doesn't work. This is a bug, and now that I think of it, it was probably reported close to a year ago, although I can't find a reference to it.

If you turn debugging on in the CF Administrator and look at the generated query on the list form, you will see that the criteria in the WHERE clause is "0 > 1", which evaluates to false. So it appears that the DisplayList custom tag can't handle date range searches at this time.

As far as the other problem, trying prefixing the fields with the table names and see if that might help (tablename.messageSentTo, etc.)

Jeff






Mark Fuqua wrote:
Hey there,

I am having some troubles with date ranges on PLUM search forms and also
with trying to get multiple filters on a whereClauseExtension of the
<cf_displayList>.

When I use search by date range on a search form, the list posts with no
records and the message that "you didn't enter and search criteria".

When I use the whereClauseExtension of a <cf_displayList>, and I try and use
AND, it doesn't seem to work.   For Example:

whereClauseExtension="messageSentTo = #session.UserId# AND messageStatus =
'new'"

Chances are good that these problems are of my own making, however, I am
just wondering whether anyone else has had such problems.  Searching for
solutions is almost becoming fun.  I am just trying to make sure solutions
exist.

Thanks all,

Mark Fuqua



**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:

http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************



**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:

http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************

Reply via email to