G
Guest
I am working with a database that uses dates and times frequently. Users are
entering times into fields (InTime, OutTime, etc.). I have read some posts
that say it is always best to store a date with a time. I was not aware of
this. The date and time are separate fields in the form/table; the form is
for a single day's events, and code on BeforeInsert populates each record
with that date when a new record is created, etc.
Should I be storing the date in each time field? If so, what is the best
way to do this? So the user enters the time only, in 24hr format, but the
table stores the date in the same field. I want the time fields to be blank
before the user enters anything. Is there something I could do with the
format property, input mask, or default value, or perhaps code something on
AfterUpdate (i.e. Me.InTime=[Date]+[Time])
Does anyone have any suggestions on the best way to handle this?
Thanks in advance.
DEI
entering times into fields (InTime, OutTime, etc.). I have read some posts
that say it is always best to store a date with a time. I was not aware of
this. The date and time are separate fields in the form/table; the form is
for a single day's events, and code on BeforeInsert populates each record
with that date when a new record is created, etc.
Should I be storing the date in each time field? If so, what is the best
way to do this? So the user enters the time only, in 24hr format, but the
table stores the date in the same field. I want the time fields to be blank
before the user enters anything. Is there something I could do with the
format property, input mask, or default value, or perhaps code something on
AfterUpdate (i.e. Me.InTime=[Date]+[Time])
Does anyone have any suggestions on the best way to handle this?
Thanks in advance.
DEI