G
Guest
I am constructing a database that will handle schedules of techical resources
required at meetings. I realize that this is a job that is GREAT for Outlook
to handle, but for other reasons, we're looking to originate the scheduling
process with a database.
I have two fields (MtgStart and MtgEnd, both are Date/Time <short date>)
where I would like to make use of the start and end time portion of the
field, but have them use a common start date. Ideally, the user input form
(named: frmInput) is going to have a single "Meeting Date" field (named:
txtMtgDate) and then a "Meeting Start Time" field (named: txtMtgStart) and
"Meeting End Time" field (named: txtMtgEnd), since this will be least
confusing for the user.
What would be the best way to isolate these portions of the Date/Time fields
to accomplish this update? Philosophically, would it be better to instead
use a single Date/Time field for the date and then instead handle the time
element with two integer fields for the start and end times?
required at meetings. I realize that this is a job that is GREAT for Outlook
to handle, but for other reasons, we're looking to originate the scheduling
process with a database.
I have two fields (MtgStart and MtgEnd, both are Date/Time <short date>)
where I would like to make use of the start and end time portion of the
field, but have them use a common start date. Ideally, the user input form
(named: frmInput) is going to have a single "Meeting Date" field (named:
txtMtgDate) and then a "Meeting Start Time" field (named: txtMtgStart) and
"Meeting End Time" field (named: txtMtgEnd), since this will be least
confusing for the user.
What would be the best way to isolate these portions of the Date/Time fields
to accomplish this update? Philosophically, would it be better to instead
use a single Date/Time field for the date and then instead handle the time
element with two integer fields for the start and end times?