You can force one and only one value to always be selected by:
1. displaying the date in question in a ListBox 2. select a single date 3. Go to Properties of the ListBox and on the General tab tick 'Always one selected value'
You can force one and only one value to always be selected by:
1. displaying the date in question in a ListBox 2. select a single date 3. Go to Properties of the ListBox and on the General tab tick 'Always one selected value'
also, make sure that one date is selected when you save the .qvw... this will ensure that always one is always selected, and never can none be selected.
BUT, why do this? wouldn't it be better to allow the user to make selections? What if I want to see totals for the entire month, or just Tuesdays, or months beginning with J?
Good point Anthony. The only scenarios I've ever implemented using 'Always one selected value' are scenarios revolving FX rates for dynamic currency conversion throughout a document or language selections for multi-lingual applications. I.e. scenarios where it simply makes no sense to have anything more than one value selected for any type of analaysis. Food for thought.
My application uses a template .QVW. The values are not known until data is explicitly loaded.
I would like to restrict a particular date field to a single value, but the 'Always one selected value' option is not possible here since I don't know ahead of time what the value is. There is no data in the template, so I can't select an initial date.
I suppose it might be possible to initialize the date and then use macro code to check the 'Always one selected value' option, but this seems rather ungainly (assuming it's even possible). My current solution is just as ungainly: the field event trigger OnSelect calls a macro which enforces the single selection.
The 'Always one selected value' is a tantalizing feature, but it is not complete without some way to initialize the data.
