Procedures::Date_cnvrtd > GetasDate ( "1/1/2011" )
Procedures::Date_cnvrtd > Date ( 1 ; 1 ; 2011 )
will work. "1/1/2011" is not evaluated as a date as dates are stored internally as a number counting the number of days elapsed since an early arbitrary date so your current expression is comparing an integer number to a block of text.
Id suggest that you could add a set of date fields set to global storage _disp_BeginDate _dispEndDate
Then create a realtionship with the current key and Procedure::Date >= _disp_BeginDate and Procedure::Date <= _dispEndDate
Setting the begin and end dates can be done in a variety of ways.
Add these global fields to your main table.
If you use aammondd's very good suggestion, be sure to use an OnObjectExit or OnObjectSave script trigger on both date fields to perform this script to force the portal filter to update each time you change a date in one of these fields:
Refresh Window [Flush cached join results]
Wouldnt OnObjectModify be better?
Only if the only way you can select a date is by selecting one from the drop down calendar. OnObjectModify will "fire" with each keystroke, so it's not a good option if the user is able to enter data directly from the key board.
Thanks for that note I so rarely use keystrokes to update my global display keys that i havent experienced these issues.
Thank you PhilModJunk and aammondd. The fuzzy nooby haze is slowly lifting. I appreciate your help.