Not sure if I read it in this project blog or elsewhere, but never ending recurring events can cause huge storage needs. First consider that recurring events always have to deal with the exceptions - say, over a holiday period or conflicts with vacation or another activity.

There are various ways for dealing with these, but one technique (I do NOT know that this is what DNN uses however) is to take a recurring event and write out all the individual events - making exceptions easy to deal with. This requires having an end date, and should mention that far off end dates (e.g., Dec. 31, 2999) could chew up lots of storage space unnecessarily.

I suspect you are right about the DNN Events module. As far as I've seen it handles recurring events but not deviations from that pattern.

I was referring to more sophisticated programs that do handle exceptions and allow you to change one or more instances of an event without killing the normal recurrance. If you've Microsoft Outlook, for instance, you can manually change a meeting date that falls on a holiday.

I do NOT know the DNN events module very well, I'm just speculating that this MIGHT be a reason they need an end date, if they plan to add exceptions to recurring events in the future.

- J