I usually provided interface logic that allows the user to specify a recurring event, but then actually used separate database records to record events as separate records on an SQL server.
In other words, they can indicate a meeting every Monday evening at 7 pm, but I am recording 52 entries per year so that individual meetings can be changed, deleted, or added additional information to these events.
I provide methods that allow the user to cancel all future events, and then re-enter a new repeating series, if necessary.
I have not come up with the perfect way to handle this, so I will follow this thread to see if any big suggestions are coming up.
source share