Hi, I'm an ICT manager in the World Health Organization. We haven't directly purchased the Telerik Scheduler control but another company (ESI) has used it in implementing a project for us. It's pretty good in some respects, but the recurrence rule parsing has more holes than Swiss cheese! In searching through your forums I can see some of them have been reported to you and apparently you haven't done anything about them. For example, events scheduled to recur once every second week recur once a week instead. This has been reported to you twice:
http://www.telerik.com/community/forums/aspnet-ajax/scheduler/bi-weekly-recurrence-not-working-correctly-using-expandrecurrence-function.aspx
http://www.telerik.com/community/forums/aspnet-ajax/scheduler/error-while-using-expandrecurrence-function-from-production-sql-server.aspx
But you redirected those threads to another thread that addresses a completely different issue, here:
http://www.telerik.com/community/forums/aspnet-ajax/scheduler/recurrencerule-and-timezoneoffset.aspx
Anybody looking to do a serious number of recurrences with your software will be very disappointed. Sometimes recurrences show up in the day view but not the week and month view, or visa versa...
My recommendation: in addition putting some work into fixing the many problems with recurrence parsing, I recommend that you disable the "no end date" option to force users to choose either an end date or a number of occurrences, then save a separate database entry for each occurrence, linking them with a recurrence ID. Your competitors do this with much better results.
http://www.telerik.com/community/forums/aspnet-ajax/scheduler/bi-weekly-recurrence-not-working-correctly-using-expandrecurrence-function.aspx
http://www.telerik.com/community/forums/aspnet-ajax/scheduler/error-while-using-expandrecurrence-function-from-production-sql-server.aspx
But you redirected those threads to another thread that addresses a completely different issue, here:
http://www.telerik.com/community/forums/aspnet-ajax/scheduler/recurrencerule-and-timezoneoffset.aspx
Anybody looking to do a serious number of recurrences with your software will be very disappointed. Sometimes recurrences show up in the day view but not the week and month view, or visa versa...
My recommendation: in addition putting some work into fixing the many problems with recurrence parsing, I recommend that you disable the "no end date" option to force users to choose either an end date or a number of occurrences, then save a separate database entry for each occurrence, linking them with a recurrence ID. Your competitors do this with much better results.