Dan I have done what you're suggesting on other forms that are meant to add/edit data in a table. These forms however are only meant to collect variables for use in a program, so there IS NO column to set to the default.
David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "Dan Goldberg" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, August 16, 2004 2:46 PM Subject: [RBG7-L] - RE: Setting Default for Variable Date Picker Leaving NULL as Option > I used a db edit field to set the default. Then I set the db edit field > default to .#date for today. I hide the db edit field if I do not want the > user to see it. > > Dan Goldberg > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of McClure, > Cheryl > Sent: Monday, August 16, 2004 11:40 AM > To: RBG7-L Mailing List > 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) > >
