> Kreig's advice is spot on! > > If you think the application through, I believe that you will come to > the same conclusion.
Many thanks to everyone that responded to my post. After reading through everyone's suggestions I've decided to follow Kreig's advice of creating a database record for every occurrence of an event. This will obviously simplify my database logic when querying for events and also allows for better data indexing, something that my early ideas did not do well. This approach will also allow me to add unique comments for each occurrence of an event and potentially track information about each event's attendees. One question for you Kreig: when a recurring event is added to the database a number of inserts must be run. In your application, how far "down the road" did you create records in the DB? If an event is to take place every Monday with no definite end date specified, how many records did you create? A year's worth? Two? Thanks again for everyone's input, Seth Petry-Johnson Argo Enterprise and Associates ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
