Featured Post

Customizing the Sumatra Double Booking cmdlet

There are a simple ways to customize the Sumatra Double Booking cmdlet, and most of them involve a text editor. Let's look at the mess...

Monday, November 20, 2006

Send As... permission and Exchange Hotfixes

For Rhino users and Sumatra Exchange Pump users, and Sumatra Utilities users, Microsoft's various post-sp2 Hotfixes for Exchange 2003 have been causing havoc with the Send As... permissions necessary to put calendar data properly into Exchange.

Good has the best summary we've seen of how to deal with this:


Wednesday, November 15, 2006

cdoEndByDate Broken

Usually we like to report things that can get fixed. But as we've discovered, fixes to Collaboration Data Objects (CDO) just are not to be hoped for.

We were attempting to create recurring banners in Outlook using CDO server-side.

As this sample code illustrates, the error comes from CDO directly.

Set oApp = New CDO.Appointment
oApp.Configuration = iConfg
oApp.StartTime = CDate("10/4/2006 10:00:00 AM")
oApp.endtime = CDate("10/4/2006 11:00:00 AM")
oApp.Duration = 1 * 60
oApp.Location = "My Cube"
oApp.Subject = "Test: Create Meeting in VB.NET"
oApp.TextBody = "Hello..."

' Add recurring appointment
Set iRPatters = oApp.RecurrencePatterns
Set iRPatter = iRPatters.Add("Add")
iRPatter.Frequency = CDO.CdoFrequency.cdoWeekly
iRPatter.Interval = 1 ' 1 hour from 10 to 11
iRPatter.DaysOfWeek.Add (3) ' every WED
iRPatter.PatternEndDate = CDate("10/25/2006 11:00:00 AM")
iRPatter.EndType = cdoEndByDate

Our recommendation: create them as non-recurring entities and inform users if they want to make them recurring. Since Outlook does not use CDO to interface with Exchange (ever wonder why Microsoft released CDO in the first place?) that will work.