........... problem... can no longer see the events in the datepicker... asking for metrics seems even slower than previous method. The empty datepicker is now just a navigation tool whereas before it gave a visual guide as to the existence of events.

 

It seems a classic case of dammed if I do dammed if I don't.  I suspect even after all your help I am going to hav to leave it as it was. I'm going to sleep on it.

 

 

Regards and thanks again!!!!

 

 

 

 

 

I have set this to 3. Users preference. They previously had this to many as could fit but I have pruned that back as I had spotted the correlation between performance and display. See one of my earlier replies.

 

Regards

 

Try to restrict to one - you have arrows to switch months and even arrows to switch years if you use flag

 

    wndDatePicker.YearsTriangle = True

switch Calendar to MonthView and scroll it Up or Down - you will see difference - now it going faster - DatePicker not block scroll till DatePicker update it's state

  

 

 

In 2007 there are upto 20 events for every weekday. In 2008 this grew to a figure slightly over that. If the user clicks the datepicker arrows to go back to a month in 2007 the datepicker does not release the calendar until the datepicker has updated. I have reduced the number of vertical rows to 3 in an attempt to prevent the datepicker taking too long to update.

 

Switching off the flags as you suggest does seem to offer a minor improvement nut nowhere near enough.

 

I don't use MFC if that helps.

 

Best regards and thanks for all your assistance.

 

boolean BoldDaysWithEvents;
boolean BoldDaysOnIdle;

[in MFC case: m_CalendarController.SetBoldDaysWithEvents(FALSE); m_CalendarController.SetBoldDaysOnIdle(FALSE);]

 

If datePicker will respond only on Calendar selection - it will be faster.

 

 

I don't see why it should be necessary to do that, it obviates the datepicker and that is supposed to have been designed to let the user do exactly what they are doing...but thanks anyway.

 

Regards

 

I'm sorry I didn't explain, my datepicker is attached to the calendar.

 

It seems as though when you first attach the calendar the dates are populated from that date forward.

 

However, if my users jump to a date two years in the past the controls try to populate everything in between and locks the application until all dates are populated. This is far too much of a wide range of dates to populate. I am asking if there is a way to limit the number of months/days that are populated at any time. i.e. the the amount of dates in the datepicker ? Am I explaining this ok?

 

Regards