CRITICAL: Applications will run up against the "object model
guard":
Your applications will encounter the
object model guard
whenever you access certain objects and methods, especially those
related to addresses and sending items. At the very least, you will
want to update your applications to handle the error that Outlook
raises when a user clicks No in one of the confirmation prompts.
In an Exchange Server or HP
OpenMail environment administrators can set up
administrative overrides
for the built-in security settings. Otherwise, the only workarounds
are to use a different programming model --
Redemption or, for
C++/Delphi only, Extended MAPI -- or code or
a tool that uses SendKeys to automatically click the prompts.
Office XP Service Pack 3
adds Body and HTMLBody to the list of properties subject to the
Outlook Email Security Update for VBA and
external code. On published forms, HTMLBody is subject to security prompts, but Body is not.
The administrative security components have been updated to
allow for "trusted" COM add-ins, but CDO is unaffected.
If the administrator in an Exchange Server or HP OpenMail
environment uses the updated
security components to trust a COM add-in, certain CDO calls
still remain subject to the "object model guard" prompts.
Some large complex forms may truncate data or be unpublishable
on Windows 98 and Windows ME:
On Windows 98 and Windows ME, the Body property can hold only
64kb. You may also be unable to publish a form. See:
There
may be discrepancies between the data added to the Body property and
what you read out programmatically:
This is related to the first KB
article listed above:
In addition, on Windows 98 and
Windows ME, Outlook 2002 adds an Asc(13) character to the end of the
Body property. This does not happen in Outlook 2000
On Windows 2000 and Windows XP,
Outlook does not truncate the Body property when you read it
programmatically, but it adds two characters -- Asc(13) and Asc(10)
-- to the end. This does not happen in Outlook 2000
The Registry key for the Master Category list has moved ...
again:
If you have a project that enforces a single Master Category list
for all users, you need to be aware that the Registry key changes in
Outlook 2002. The list is located at the HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Categories\MasterList,
but the key has changed from a string value to a binary, to
accommodate Unicode values. Under Outlook 97 and Outlook 98, the
category list was stored as a semi-colon delimited string in the
default value for the HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Outlook\Categories
key. Under Outlook 2000, the list was a string value --
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Categories\MasterList.
The XPrint control and add-in for printing custom forms are not
supported:
According to the article
OL2002 XPrint Control and Add-in Unsupported with Outlook 2002,
the XPrint control and add-in for printing custom Outlook forms have
not been tested with Outlook 2002. They might work, but then again,
they might not. They are officially unsupported. See
Printing Custom Outlook Forms and Reports
for alternative methods.
The Help system is awful ... still:
The HTML help for Office XP has been redesigned, and in the
process, someone decided to remove all the information about the
Office VBA constants. So if you want to know what constants to use
in your VBScript code on Outlook forms, you won't find them in Help.
Instead, use the object browser in VBA, or see
Microsoft
Outlook 2002 Object Model Constants.
There are also errors in help that have been there since Outlook
97. See
OL2002
Documentation Errors in Outlook Visual Basic Help.
Contact
form preview:
In Outlook 2002, a contact form with the first page customized will
not display in the preview pane.
This is addressed in SP3, even for forms with code behind them. See:
You
cannot create new Office Document forms:
The File | New | Office Document
command in Outlook 2002 creates an Excel, Word or PowerPoint
document, not an Office Document form as in previous versions. You
can, however, work with existing Office Document forms in design
mode in Outlook 2002. If you want to continue to design new Office
Document forms, one solution is to create blank Office Document
forms in Outlook 2000, publish them then transfer them to Outlook
2002 either as forms published to a folder in a PST file or as .fdm
files.
We
have put together a Personal Folders PST file containing six blank
sample
Office Document
forms. After you download the file, unzip it, and open the
Office Document forms.pst file in Outlook using the File | Open |
Outlook Data File command.
The
Office Document method of codeless printing of Outlook forms still
works with Excel worksheet forms, but using a Word Office Document
form as a response form appears to hang Word.
Also see:
Outlook
2002 allows only 30 entries in the Links collection:
Without saying how many links were allowed in earlier versions,
Microsoft has introduced a limit in Outlook 2002 "for performance
reasons." When working with the Links collection, you may want to
check the Count before adding a new Link. See
OL2002: You Cannot Link Multiple Contacts to an Item.
Users
cannot toggle a folder home page on and off:
This could be a problem or a feature, depending on your point of
view. See
OL2002: Cannot Toggle or Disable Folder Home Page.
Shortcuts
and embedded objects in tasks don't work:
In Outlook 2002, embedded objects, shortcuts, etc. in task items
cannot be launched after the item is saved and reopened. No known
workaround. |
