My question is two-fold... first, is there a better control or method for
accomplishing my goal and second, can anyone point me in the right
direction
for how I actually get the form code to then creat multiple records - one
for
each date selected?
You might not need to store and create a record for each date of the
booking?
It is FAR less work to simply have a booking record, and you enter the
start, and end date.
And, further why would put the event information in each record? The idea of
using a relational database is to NOT repeat data you don't have to.
So, all that event information does not, and should not be repeated.
About the only thing you are not clear on here is are event bookings
*usually* consecutive dates, or do they tend to have gaps?
There is nothing stopping you from write code that creates a record for each
date when you press you "booking button", but then if you have to change a
date, then you might have to add a bunch more records at the start, or end
of the booking (depending on which end you changed).
Without question, you will need some VBA programming skills here to
accomplish this.
However, do believe that just having a booking record with the start and end
date is MUCH less work. If you have a 5 day booking, then the end result is
that you would have to write lots of code to add/remove records if you
create a record for each day of that booking. This can be a LOT of work. If
you just create one record, and inside the record put in the start and end
date, then you can have a form that lets you edit this date range, and no
adding/deleting of records for each day need occur. And, to delete the
booking, you only have to delete the one record. To change or extend the end
date....again, you just change the end date (no adding, creating/deleting of
a whole bunch of records is required).
It is very important to realize that my design suggestion may NOT help you,
and this would be especially so if booking NEVER span several days, or if in
fact each day the user requites a different booking unrelated to each day.
So, not knowing if most often a booking spans several dates, or in fact each
booking date is a separate kind of thing would effect the choice of design
here. I am only stating that if your booking do span several days at a time,
then store start/end date, then this approach is a ZILLION times better then
storing a record for each date (again, assuming that bookings can, and do
often span several days).
The other big advantage of storing a start/end date is that you can find
collisions a LOT easer. And, of course, last but not least, if you can just
store the start/end date...you can edit the booking with a form, and not
have to create all those little records..