Hi, Howard and thanks for the input... Tell more more about the "Exceptions" table. How do you see it being setup and how would it's data be used for processing?
Rick -----Original Message----- From: Owens, Howard [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 4:01 PM To: CF-Talk Subject: RE: RE: How to handle Calendar Scheduling of Recurring Events? This is just what I was thinking ... three tables .. -- One_Time events (could also contain multiple instances of same event that are not, specifically, recurring) -- Recurring events (stores info needed by CF code to build monthly calendar) -- Exceptions table (stores user-input info on specific dates that scheduled recurring events are canceled (one entry) and rescheduled (second entry) CF code would build (though maybe it would be better to do in a stored procedure), say, a daily calendar by first pulling recurring events that meet the criteria for running that day, then checking the exception table, then mixing in that day's one-time events. This meets the needs of recurring events without dumping a whole bunch of dates into one table, and allows users the ability to reschedule recurring events. On the user interface, when the user logs in, the user gets a hit list of upcoming events (recurring or otherwise) within that users domain for, say, 90 days out, and each one can be individually edited. H > -----Original Message----- > From: Matt Liotta [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 12:07 PM > To: CF-Talk > Subject: RE: RE: How to handle Calendar Scheduling of Recurring > Events? > > I would probably implement some sort of recurring exception table to > keep up with things like that. > > Matt Liotta > President & CEO > Montara Software, Inc. > http://www.montarasoftware.com/ > 888-408-0900 x901 > > > -----Original Message----- > > From: Rick Faircloth [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 15, 2003 2:11 PM > > To: CF-Talk > > Subject: RE: RE: How to handle Calendar Scheduling of Recurring > Events? > > > > Hmmm... > > > > If you have an entry in the one table that doesn't have a specific > > date, but is for the "2nd Tuesday of each Month", I can see how you > > could code to create specific instances dynamically for display, but > how > > would you allow for changing from the 2nd to 3rd Tuesday for a > specific > > occurrence? That instance that is changed has to become a separate > > record. Would that happen if the user chose to update the dynamically > > created "faux" display record? And when it did, would that event be > > inserted > > back into the table as a "one-time" event? > > > > Rick > > > > > > -----Original Message----- > > From: Matt Liotta [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 15, 2003 1:40 PM > > To: CF-Talk > > Subject: RE: RE: How to handle Calendar Scheduling of Recurring > Events? > > > > > > > You're suggesting one table for everything? > > > > > One method for everything, which may be implemented using a single > > table. > > > > > Wouldn't that pattern have to be turned into specific occurrences at > > some > > > point? > > > > > Of course, at runtime when generating a calendar view for instance. > > > > -Matt > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
