I've got to take some time to look at your two table approach, Joshua. Haven't had time to think about it...got called out for some "network admin" work by a client...
Got to consider your dropdown solution for the "2nd Tuesday of each month" problem...but one concern would still be how to allow them to change a specific occurrence of a recurring event...like changing this month's "2nd Tuesday meeting" to the "3rd Tuesday. I guess you're suggesting allowing the insertion upon submission of all the specific occurrences of a recurring event for a specified time period? To allow for alteration of specific occurrences without affecting all? The only problem I can see with using the info from the dropdowns to create all the specific occurrences would be that once those specific occurrences that populate the db have passed their date, say for 2 years, another submission of "2nd Tuesday of each month" would have to occur to create more specific events. Just to make sure you were following my probably unclear logic on two tables... I was suggesting having only one table that actually contained events that would populate the calendar. That table would be populated by manual entries from users, but also by "automated" entry from a second table that held "descriptions" of recurring events. The information in the "descriptions" table of recurring events would be checked when the calendar was called up and the actual events involved for the display period would then populate the calendar. That way, there may be "descriptions" of recurring events, that when actually turned into specific calendar events, would turn into 500 events over two year period. However, the 500 events wouldn't be entered into the actual events calendar until someone wanted to look at that time period. So if no one wanted to see Feb 2004's events until Dec 2003, the events table wouldn't actually contain those event records until Dec 2003 when the calendar was called up for that period. Make any sense? That way, too, when the specific events are "created" from recurring events in the "description" table, they could be altered for that specific occurrence without affecting future creation of recurring events. Weaknesses in this approach????????? Rick -----Original Message----- From: Joshua Miller [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 2:43 PM To: CF-Talk Subject: RE: How to handle Calendar Scheduling of Recurring Events? Personally, I would advise AGAINST using 2 tables for event storage ... It could get messy. If you use the link table then they're all treated the same, you just select everything from the tblEventDates table that's within the current date range that the calender is displaying or searching. If there's only one instance then that's fine, if there are 30 then that's fine too - it's all the same. I would think that using 2 tables for storing the "events" would be pointless. You could accomplish the same thing using one table for events and one for event dates. For "First Tuesday of Each Month" you would just need to (perhaps) predefine a list of these types of events. Maybe 3 fields on the form: [number] [day of week dropdown] [datepart dropdown] Ie: [2] [Tuesday] [Month] [SUBMIT] Then use CF to pre-determine the dates for the timespan before shoving them in the dates table. Just my opinion though, worth what it cost you :) Joshua Miller Head Programmer / IT Manager Garrison Enterprises Inc. www.garrisonenterprises.net [EMAIL PROTECTED] (704) 569-9044 ext. 254 ************************************************************************ ************* Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Garrison Enterprises Inc. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to [EMAIL PROTECTED] ************************************************************************ ************* -----Original Message----- From: Rick Faircloth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 11:54 AM To: CF-Talk Subject: RE: How to handle Calendar Scheduling of Recurring Events? I'm going to have to give all the input some thought... a lot of good input...thanks, everyone. A couple of notes: This calendar function doesn't have to bother with overlapping events or show duration. Just when it starts. So duration doesn't have to be a factor like it would be in a scheduling function for a room or something like that. Also, I don't *think* anyone's approach so far has addressed a problem with how many recurring community events are scheduled...e.g. "First Tuesday of each month"... That causes the date of each month to be different depending on the month. I guess I could just code the function to find the date of the "First Tuesday of each month", then I'd be set. Right? Another thing... How about having two tables for the app...one that holds "one-time" events and another that holds recurring events with extra fields for denoting frequency, etc. Then when the calendar processes, output events from the table of "one-time" events, then have the code search the table of "recurring" events which have events matching the display date range...say for the month of February. Joshua, you hit upon a problem of rescheduling a recurring event for just one of the times it happens...e.g. next month's meeting will be rescheduled from the "2nd to the 3rd Tuesday of the month". The only way to allow rescheduling would be for the event to have an actual record in the "one-time" events table. That could happen if the recurring events table mentioned above was used to insert specific instances of a recurring event into the "one-time" events table. That table would then provide the event data for display. (That's the first way I can think of immediately...) Finally... Like Neil suggested and Joshua pointed out, in order to have "granular" control over event date/time changes, I could just allow all recurring events to be inserted as individual occurences in the db, for up to, perhaps, the next 2 years, which would allow annual events to be schedule for the next 2 years, and would keep the table down to about 5,000 events covering 2 years, assuming about 50 events per week, both one-time and recurring events. Then, with each passing week, when the calendar is processed and displayed, the code adds another week's worth of events from the recurring events table. It would amount to keeping 2 years worth of records in the table at once. If required by a client, the time-span of 2 years could be increased if they needed to show more years for recurring annual events. ??? Of course, if scheduling certain locations and times was an issue, then the code could be adjusted to check for conflicts... More thoughts? Rick -----Original Message----- From: Joshua Miller [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 9:59 AM To: CF-Talk Subject: RE: How to handle Calendar Scheduling of Recurring Events? Actually, rethinking things, a multi-insertion isn't all that bad of an idea - just using a linked table. What if the event has one day out of the recurrence that's an oddity - like if they need to push a Monday meeting to Tuesday one week. If it's a multi-insertion then you could actually let them edit the individual instances of the event by adding another record to the events table and then perhaps reference a "alteration" to a particular event. I think that using a linked table with only dates would give you more granular control over the individual event occurrences. In real life, things get pushed and shoved around to fit into schedules. If they don't get edited then it's no big deal, using a linked table doesn't actually use a whole lot of storage space. Besides, drive space is cheap, processing power is more costly. Joshua Miller Head Programmer / IT Manager Garrison Enterprises Inc. www.garrisonenterprises.net [EMAIL PROTECTED] (704) 569-9044 ext. 254 ************************************************************************ ************* Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Garrison Enterprises Inc. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to [EMAIL PROTECTED] ************************************************************************ ************* -----Original Message----- From: Robertson-Ravo, Neil (RX) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 9:49 AM To: CF-Talk Subject: RE: How to handle Calendar Scheduling of Recurring Events? nah, dont worry, us Celts have thicker skin that that... I did see what you meant, and I didnt mean it to be a multi insertion etc.... -----Original Message----- From: webguy [mailto:[EMAIL PROTECTED]] Sent: 14 January 2003 14:47 To: CF-Talk Subject: RE: How to handle Calendar Scheduling of Recurring Events? > Thats just stupid Sorry that sounded rude when I reread it! I'll post my solution in a mo. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
