No question that you should store date and time in the same field. If/when
you only want the date portion or the time portion, use the DateValue or
TimeValue functions as calculated fields in a query.
To avoid double-booking, take a look at what Allen Browne has at
http://www.allenbrowne.com/appevent.html
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
"Hicksy" <(E-Mail Removed)> wrote in message
news:8B38658A-EE85-4B53-99DF-(E-Mail Removed)...
> Hi everyone!
> I am setting up a vehicle bookings database and a very important part of
> it
> is that when a user books a vehicle, the date and time 'in' and 'out' must
> be
> verified to avoid double bookings. Would the best way to tackle this be to
> set up a general date field with both the date and time together for the
> 'in'
> and 'out' fields. Would it then be possible to look at these fields to
> distinguish if the vehicle is already booked at a certain time?
> Thanks