Cheryl, For as long as I can remember now I have always set a default date to force a change to the correct date. (If you've been following another thread you'll know it's 01/01/1900.) Most of my data is now pre-entered with defaults and then edited rather than entered as a new row. I find this generally easier to handle but, as always, there are exceptions.
With the exception of one table where I keep track of the date a change was made, my dates do not (usually) need to be changed (once re-set from the default) so I don't really have any problems with the date-picker. Nevertheless, like others, I find the date-picker's behaviour a little strange. It seems to me that the date displayed would automatically be assumed by any user to be the date that will be saved - no matter how you exit from the object. No doubt others will have their say but, it seems to me, that a request for a change would be welcome. Regards, Alastair. ----- Original Message ----- From: "McClure, Cheryl" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, August 16, 2004 7:40 PM Subject: [RBG7-L] - RE: Setting Default for Variable Date Picker Leaving NULL as Option Sorry David, I can't offer you a solution but I am trying to solve a similar problem. 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? Cheryl -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David M. Blocker Sent: Monday, August 16, 2004 1:57 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Setting Default for Variable Date Picker Leaving NULL as Option Here's the problem: I'm using variable Date pickers for these fields. The user is most cases is NOT required to include the date in the search criteria. Now it works fine - even though a date shows in the picker, unless they click on it to change it, the variable actually is NULL when the user exits the form. ONLY if they click on it and change the date manually or by the calendar is the variable set to a date. So the calling program can check for the variable NULL or NOT NULL and build the where clause accordingly. In fact, I actually have a message box on the form warning them that even the date showing is the one they want, they must click on the picker to actually select it. (If you don't, the variable remains NULL)
