Featured Post

Three Basic Ways of Dealing with Double-Booked Resources in the Sumatra cmdlet

There are three basic ways of automatically dealing with double-booked resources in the Sumatra cmdlet suDoubleBookedMeetings. You guys wo...

Monday, March 28, 2011

Oracle Calendar Migrations and Long Resource Names

Kudos to the team at North Dakota State University for finding a bug!

If your Oracle Calendar resource name is longer than 32 characters (and those 32 characters were the same as some OTHER resource's) we weren't handling the error condition gracefully.

That is fixed in version 5.1.01 of xCalReader.

This is probably not an issue for most teams in migration but if you do not have the latest version and want it just contact us.

No comments: