I am going back into some older, simple forms that are using filtered selects and I am still having some problems with
RC2, even though the release notes say you fixed this. The scenario is using a whereClauseExtension in a Filtered Select
menu. I drill down from OfficeList -> OfficePhoneList to add one or more phone numbers for the office. I want the
filtered select to default to the Office I just drilled down from, so I add a whereClauseExtension to the filtered
select tag as follows:
whereclauseextension="Office.OfficeID = #Session.OfficeID#"
This creates a result set of zero because the whereClauseExtension always forces the select statement to evaluate to
false and return zero records.
The filtered select query without the whereClauseExtension looks like:
SELECT Office.OfficeID
FROM Office
WHERE 0 > 1
ORDER BY Office.OfficeID
With it, it looks like:
SELECT Office.OfficeID
FROM Office
WHERE 0 > 1 AND Office.OfficeID = 662
ORDER BY Office.OfficeID
That is always going to evalute to zero, isn't it? Should be 1 > 0? I changed line 160 in the DiplayFilteredSelect tag
to '1 > 0' and I get back the one record I am looking for.
Jeff
**********************************************************************
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
**********************************************************************
