Sorry, didn't answer your second question.

Recurring events are just a single call to EventsRecurMasterSave and multiple calls to EventsSave. The challenge is the logic behind recurring events and that depends on how complex you want to make it. You can use code from the existing module (it's open source), but I don't believe there are simple calls to existing code you could make that would just do it for you.

All Events records are single events. It is EventsRecurMaster that pulls them together and makes them an editable sequence. The recurrence information stored is essentially based on RFC5445 (the iCal spec), which you would need to understand to a reasonable level to ensure correct creation of records. Note that not all RFC5445 RRULE permutations are supported by the module.

---

DNN MVP
Events - Get the latest version - Upgrade now!!
Feedback 6.4.2 - Now available - Give it a go!
Find us on Codeplex - DNN Events, DNN Feedback

---

Requirements/Bugs - Please submit them on Codeplex

OK, thats for another day but if I am just to add all simple events to RecurMasterID = 1 then nothing fatal should happen?

I will write an extra sub to return a new id when my patience as returned lol

---