When you create a new appointment in your calendar in Outlook 2003, by default 'All day' events show your time as 'free' and all other appointments show your time as 'busy.' Some employees at the company where I work wanted this behavior changed. Specifically, they wanted the 'All day' appointments to default to 'busy' because they schedule many meetings and other appointments that last all day and often forget to set the appointment as 'Busy' manually. This creates confusion when other employees go looking for them and they aren't in their office! I scowered Google, as I usually do when faced with tasks such as this, and could not find a nice short easy solution. Most sources (even some Outlook/Office MVPs) said there was NO way to do this (which is just not true). Others had you create custom forms, which is the answer. However, I couldn't find a custom form answer that wasn't unnecessarily LONG and difficult to implement.
So I toyed around and came up with a simple custom form that changes the behavior. Here's how you do it!
First, create your custom form, using the IPM.Appointment built-in form. If you don't know how to create a custom form, there are bazillions of good walk-throughs out there. Google for it.
Second, add the following code in the Script Editor...
Sub Item_PropertyChange(ByVal Name)
Select Case Name
BusyStatus = 2
THAT'S IT. Nothing more is required in the custom form! Publish the new form, then set the default calendar appointment form to the new one and voila!
I am currently in the process of converting the Avian Waves website from ASP to ASP.Net. In addition, the thoughts/links page has been transformed into a full-fledged blog (what you are looking at right now). Over the coming weeks, new features will gradually be added, and a new look (including the new Avian Waves logo) will start to appear. This is a large transition for me and Avian Waves, but will lay the foundation for the future of this website, my music, and the "business" side of Avian Waves.
News and notes will continue to be posted to this blog, comments can be posted by anybody, and an RSS feed is now available!
In order to keep an ongoing interest in my music, rants, tech tools, and everything else, I'm hoping this site can stay dynamic and compelling. Before you know it, I'll finally be done geeking out and I can get back into the studio and write music again. :-) It's been too long, but will be worth the wait.
The new Avian Waves website is combining together several of my personal projects into one: The music stuff, tech stuff, and anything else I can dream up!
The old website was table-based, using all the old techniques I learned in the 90s to format graphics and text for old browsers. I adopted CSS only when it was a convenient way to make things look "right." With the new website I am striving for 100% XHTML 2.0 compliance. The main portions of the site will be compliant very soon (most already are). The blog software (a customized version of Presstopia that I modified) will take longer to make compliant. It is currently 100% XHTML 1.1/Transitional compliant (I think).
Well that's all fine and dandy, but why go through the trouble?
I want the site to be styled completely using CSS so that the site's data can quickly and easily be "skinned." Eventually, I will check how the site is being accessed and offer an optimized view depending on the device. Increasingly, websites are being visited by phones and pocket devices, which can only implement a subset of layouts features that IE, Firefox, and Opera can. Since the substance of the site will just be XHTML tags styled using CSS classes, reformatting the website for other devices is as simple as referencing a different style-sheet. The easiest way for me to be flexible in the future is to strictly adopt XHTML 2.0 now.
It is very interesting balancing the way styles are used to make things look "right" under all the different browsers. I thought CSS replacing table-based layout was supposed to make that concern go away? I suppose that's another rant for another day!
Avian Waves is also moving from an ASP site to an ASP.Net 2.0 site. The reasons for this are pretty obvious: ASP.Net is faster, more robust, easier to code, and easier to debug!
Master pages are awesome...