Sumatra Development LLC

It prompts to allow a single user to remove a single category keyword or all keywords from their Calendar and Inbox data.  Please note the following restrictions:

• The only works on the Inbox and the Calendar (not Tasks, Contacts, or other mail folders)
• This has no “UNDO” function.  If you remove a category you don’t want removed you’ll need to add it manually
• Because of the way Exchange works, if this user is guest at a meeting which the meeting owner has added a category tag to AND the meeting is updated, the category label will again be added
• Visual Basic Scripts (VBA) in Outlook does have some restrictions:
  • Users can modify VBA code unless the project is password-protected.  (This can introduce support problems when users start to modify the code.)
  • There is no simple way to distribute Outlook VBA code to users. Outlook supports one VBA project at a time. The successful implementation of the VBA script depends on the users to open the Visual Basic Editor and import the modules. An alternative would be to distribute an entire project file to users, but that would mean that any previous modifications to a user's project would be lost.  If the user has existing code, they must export the code to one or more module files before loading this VBA project, or the current project will be over-written.  That said, you can send this script around to the users who experience problems with the Pocket PCs, along with these instructions how to implement the macro.

1. Copy the script. 

2. Go to Tools-Macro-Visual Basic Editor. 

3. Insert-Module and Paste the script in, OR, if you’ve chosen to download the code stored in the file “module1.bas”, you can  File-Import File-Module1.bas

4. Save it, give it a name, and execute from the Macro function

• Users who import code modules written by others will receive a warning message unless they either sign the VBA project or lower their macro security level. This message annoys users, who might lower their macro security level.  We caution against this: It exposes users (and potentially your organization) to malicious VBScript embedded in messages.
• XP Users who don’t have macro protection set properly will receive this message: The macros in this project are disabled….”  Refer to this footnote to change the macro security settings to medium[1].

 Another distribution strategy if this Pocket PC – Category problem impacts many users in your organization is to use a COM add-in.  Sumatra has converted this VBA macro into a COM add in.  This add-in will work for Outlook 2000, 2002, and 2003.  This COM add-in is available on an unsupported basis