one table to hold the event information, what where who etc...
anopther table that holds dates with an EventID to tie it back to a particular event
Also, in The Date table, I'd try something like DateID, SingleDate, StartDate, EndDate
single dates would hold a onetime date , start and end dates would hold ranges.
or even just StartDate and EndDate.. if it is a single date, put that date in BOTH fields
I had a compnay tell me it was absolutley going to be 4 day events so all they needed were date ranges... Once it was written to do just that... they needed to exclude days in that range making it just 3 single dates (or a 2 day range and a single day) and it was a pain to change! If I had just done it this way to start with, it would have been fine.
I'd suggest doing it this way just to save you the headaches for when it happens... and it will
as for a calendar app, I have no suggestions for thridparty apps since I havent used any but if you decide to write your own, here is a VERY basic tutorial to get started with that I wrote way back when but dont tell anyone : )
http://tutorial180.easycfm.com/
----- Original Message -----
From: Burns, John D
To: CF-Talk
Sent: Monday, August 09, 2004 10:04 AM
Subject: Calendar data structure
I'm looking for some advice on what sort of structure I should use for
making a calendar app. My main question is about storing the dates. To
accommodate multi-day events, is it better to do a startDate column and
an endDate column or is it better to do a single eventDate column and
insert multiple events multiple times? I will need to output this data
as "today's events", "this week's events", and a monthly calendar view.
Along the same lines, any suggestions for a CFC or custom tag that can
organize into a calendar view (or tips for writing my own) would be
helpful. Thanks to all in advance.
John Burns
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
