Hi, 

I know this is an old thread, but the subject refects exactly my problem.  I want to save my appointments to a database, so I created database structures for both Appointment and AppoinmentRecurrence.  I create the AppoinmentRecurrence through a custom window and save the recurrence in the database.  When I want to display the information in a CalendarView, I load back the database structures and create Appointment and AppointmentRecurence objects from them.  Il all works fine and I see my appointments in the CalendarView.  When a variance is created from the CalendarView, I can save the variance in the database.  Fine.  But, when I load back information, I do not know how to reassign the variance to the AppoinmentRecurrence.  I cannot set the RecurringAppointmentRoot because it has no setter.  There has to be a way to specify that an appointment is a variance of a given recurrence.  Or am I way out?

After some further investigation, I suspect that I simply cannot do what I am trying to do.  Here is my new understanding of how it works and what I should do:

1. When you want to save an Appointment, you do not translate it to a database table.  You serialize it and save the blob into a database field.
2. When you save the appointment in this way, the associated recurrence will be saved along with the appointment if this is a root appointment.
3. When I want to modify the recurrence programmatically, I load back the appointment from the database, modify the associated recurrence and save it back.
4. When I want to integrate my appointments to the calendar, I load the blobs back, convert them and simply integrate the resulting appointments to the CalendarView.
5. In the previous step, the recurrence will automatically be created and recurring appoitnments will be automatically generated.
6. Variances should be saved separately.  They may be found in the CalendarInfo object.  When they are restored, they will automatically be link to the proper recurrence.

Could you please confirm this interpretation because, if it is right, I have a lot of rework to do.

Real Forte,

I found that working with variances are a bit tricky at first, but become simple once you understand what Infragistics has done and how to reference the variance within the root appointment.

First, you need a place to hold the variance in your database table.  Either put it in a special "variance" table, or add it to your appointment table.  To hold a variance in your appointment table, you must have the following:

1.  The variance itself.

2.  Record that it is a variance, and not a single appointment (I used a boolean flag called is_variance)

3.  Reference to the initial recurrence appointment (In my table, I used a unique appointment_id field, and reference directly to it)

4.  Reference to the DATE of the original variance.  If the date is what has changed in the variance, you need to know what was the original date or you won't be able to find it within the original appointment recurrence.

Once you've stored that information, you can then tie it to the original recurrence by first loading the entire recurrence, then accessing each occurrance (assuming you've assigned the original recurrence id to the appointment_id field I mentioned above).  After loading the original recurrence, you can then find it using the following function:

public static Appointment getSubsetAppointmentForVariance(Infragistics.Win.UltraWinSchedule.Day myDay,

Appointment myRecurrenceAppointment, String strRecurAppointmentID)

{

 AppointmentsSubsetCollection ApptSubsetCol = myDay.Appointments;

foreach (Appointment mySubSetAppt in ApptSubsetCol)

{

if (mySubSetAppt.DataKey.ToString() == strRecurAppointmentID)

{

myRecurrenceAppointment = mySubSetAppt;

}

}

return myRecurrenceAppointment;

}

Now that you have the appointment recurrence, you just need to alter the original date of the variance to a possible new date...or any other items within the object!

Hope that helps!

Hi,

Well, what you describe is basically what we ended up doing.  Managing variances has a lot of side-effect, though.  It requires much code to do it properly.

Than you for your reply.