Reading Plan exports to Outlook as multiple calendar series

Graham Criddle

While researching the issue raised at http://community.logos.com/forums/t/80221.aspx I noticed something strange.

When exporting a Reading Plan to the Outlook calendar, multiple calendar entries are made as opposed to one single one.

To demonstrate I set up a plan to read through the entire NRSV in six sessions - just on weekdays.

When I exported it to Outlook and looked at the Recurrence information for today's entry I found:

So instead of something which recurred daily with the specific days shown with an endpoint based on either number of sessions or end-date it recurs weekly.

Monday's entry also shows weekly recurrence but - in this case - there is only one recurrence (correctly)

It does produce functionally correct results but it does seem a strange way to set up the calendar entries. One downside is that if I want to delete the entries from the calendar I will need to find and delete the five separate entries as opposed to just one - and I accept this isn't a big deal[:)]

Just interested to know why it was designed this way.

Thanks, Graham 

Bradley Grainger (Logos)

Just interested to know why it was designed this way.

Here are the comments from the export to Outlook code.

// Make a separate series for each weekday in the plan, because,
// when you have one series for the whole plan and you update each occurrence, the first hundred or so occurrence saves take less than a second,
// but afterwards they become slower and slower, taking a second or more each. Thus the whole export for one year takes 5 minutes on my machine.
// Doing one series for each weekday makes the export take 30 seconds or so.

This code was probably written for Outlook 2010 (or maybe even 2007!) so it's possible this inefficiency has been fixed in the latest version of Outlook. I suppose I could test that and let you know.