Recurring appointments have been an enigma for me and I need some help understanding what exactly happens when you create a recurrence.
My software stores the appointment (not serialized, but all of the properties have their own column). my question is that when I create a recurrence, does the infragistics calendar hit the new appointment event for each recurrence (therefore each appointment recurrence would be separate in the database) or does it use the base appointment and create "ghost" appointments based on the recurrence pattern. In that case I would just need the one base appointment and save the recurrence to the database loading only based on the end date (or no end date) of the recurrence.
Thanks in advance
Hello neusanjeev,
I see that this question is related to the following forum thread:
http://community.infragistics.com/forums/p/64781/329009.aspx#329009
So I will update you via the mentioned forum thread.
Thank you.
Thanks for your Sample, ya it is working fine but in my case i am working on an existing project where SP is used to save the appointment. but when i delete or update the Occurance from Recurring Appointment its not working, like when i delete the occurance in your sample also you are inserting an appointment. i am having problem what you have insert during occurance and how it is not displaying in ur calendar. can you please clear my doubts.
Do i need to insert this appointment in database in case of Update and Delete of occurance.
Hello,
I am just checking about the progress of this issue. Let me know If you need my further assistance on this issue?
Thank you for using Infragistics Components.
Hello,
Have you been able to test my sample ?
When you retrieve your data from your database you could generate manually DataSet (middle DataSet) and populate it whit your data (instead to create appointments manually ), and bind it to UltraCalendarInfo. On this way your middle DataSet will be updated automatically. When you want to update your database, you should just to merge the data of your middle DataSet within your data base. I believe that this is the easiest approach for achieving of your goal.
Please let me know if you have nay further questions.
I do not bind the calendar to the database because some of my customers have upwards of 150 users and can choose to view multiple users on the calendar at one time, so I load only a snapshot in time from the database and manually create the appointments as they are loaded in a thread.
So, in line with your answer, I'm still not sure I understand. You say that you will see one row for the recurrent appointment, which would indicate that all subsequent recurrent appointments are "ghost" appointments created in memory from the original recurring appointment? In which case I would use the Recurrence.Save method to save the recurrence against my original appointment and load the recurrence every time I load the calendar for that owner? What about broken occurrences?