At 02:40 PM 8/16/2004 -0400, Cheryl McClure wrote:
When our data entry people see the current date showing in the
variable date picker on my form, they assume they don't have to
do anything - the date has already been selected. As you stated
- it has not. I'll be very interested to see what others have
to say about your question. I would prefer some way to blank
out the date until the date has been selected. I would also
like to see the #dup option available for subsequent rows.
Any solutions out there short of a enhancement request to RBTI?
At 01:56 PM 8/16/2004 -0400, David Blocker wrote:
... can anyone think of another way?
Cheryl McClure, David Blocker and all:
The BEST approach would be to include the additional option for Variable
Date/Time Picker Properties, such as Default Value.
Then, as the developer of your application, you can decide how you would
like to manage this criteria.
Example:
01. Define a variable say vDate DATE = NULL and use Variable Date/Time
Picker on your form.
Assign Variable Name as vDate.
02. Use the following value for Variable Date/Time Picker as Effects:
Properties | Effects | Default Value | (.#DATE+15) -- or whatever date
Click [OK] to save Variable Date/Time Picker properties.
03. Save the form
04. Now let's try a few scenarios:
Scenario A.
At the R> prompt:
SET VAR vDate DATE = NULL
EDIT USING formname
-- Notice that the default value for Variable Date/Time Picker is
being displayed as today's date - 15.
If the user does not touch the Variable Date/Time Picker or
change the date/calendar, it will NOT assign any values to
vDate variable and the vDate will still be NULL.
If you close the form, the value for vDate will be NULL.
So, you know that the user did NOT pick the date.
Scenario B.
At the R> prompt:
SET VAR vDate DATE = (.#DATE+10)
-- Keep in mind that we are pre-defining the values here ...
EDIT USING formname
-- Notice that the value for Variable Date/Time Picker is
being displayed as today's date + 10.
-- If the value for a variable for Variable Date/Time Picker
is pre-defined, it will overwrite the default value.
Now if the user does not touch the Variable Date/Time Picker or
change the date/calendar, the value for vDate will be exactly
what was pre-defined. But if the user picks a different date,
it will assign that value to vDate and the variable will never
be a NULL value.
If you close the form, the value for vDate will be either the
pre-defined value or overwritten value, but not NULL.
With this enhancement to the Variable Date/Time Picker being
implemented, you can have your cake and eat it too!
Very Best R:egards,
Razzak.
P.S.
Did I mention that this is really a live example of upcoming
Update 77?
