But a date/time picker control lets you pick only a date or a time, but not both. So I'm assuming I would need separate date and time columns in my table, right? I tested and I see that I can have a date column, a time column, and a computed datetime based on those. So I'm thinking of pre-populating the fields and putting a little button next to the field where they can use the picker to change it.
Karen -----Original Message----- From: Albert Berry <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wed, Dec 31, 2014 12:22 pm Subject: [RBASE-L] - Re: Suggestions for date/time entry? Karen, try using a pair of DB Date/Time Pickers, and set the default value on entry to the row, but only if the value is NULL. That way it will keep the original values. I find that an eep on row entry works best for this type of entry. Albert On 12/31/2014 9:15 AM, Karen Tellef wrote: I don't do much with asking users to edit date/time, but I have an application where I am going to default a date and time (default to the same date, 2 hrs in the future) but I would like the user to be able to change both the date and/or the time. I'm wondering how best to structure the table (a DateTime column, or separate Date and Time?), and what controls I can put on the form to make it the easiest for them to change either. These wouldn't be power users so it would need to be easy. Thanks for the suggestions! Karen
