Customized Contact form may not run in Outlook 98 or Outlook
97:
If you customize the first page of the Contact form in Outlook
2000, Outlook 97 users will not be able to open items created with
your custom form. This is because Outlook 97 does not support
customization of the first page.
If you have mixed Outlook 98 and Outlook 2000 users and want to
customize the first page, you must remove the Contacts button and
text box from the bottom of the page. These are for the Links
collection introduced in Outlook 2000 and are unsupported controls
in Outlook 98.
CRITICAL: Contacts folders can contain distribution list items:
This means that any code that loops through all items in a folder
and assumes that all items are Contact items will break. Easy to fix
by checking the Class of each item.
Actually, you should be careful with this in any folder, since
any folder can contain Post items, in addition to the normal item
type(s) for the folder. See these MSKB articles:
Some complex forms won't run:
A complex form with many formula fields that runs fine in Outlook
98 may not update all the calculated fields in Outlook 2000. I think
we're reaching the storage limits hinted at in the MSKB article
PRB:
E_FAIL on SaveChanges() with Too Many Properties. One workaround
is to use Text fields rather than calculated fields and do the
calculations in VBScript code. Another would be to create ActiveX
controls to do the data manipulation and add them to the form.
In Corporate or Workgroup mode, adding a recipient during the
Application.ItemSend event results in a "no transport
provider" error:
If you add a recipient (such as a mandatory Bcc) during the
Application.ItemSend event, it is not resolved and therefore results
in a "no transport provider" non-delivery report. This one
is easy to fix by doing a ResolveAll as part of the procedure. In
IMO mode, adding a recipient in Application.ItemSend works fine
without resolving.
If you set the Body property of a Plain Text message, the
message format switches to Rich Text; there is no way to switch it
back to Plain Text:
If you set the Body property in code like this:
Item.Body = Item.Body & "
more text"
the EditorType reverts to RTF. The Help file says that it reverts
to the user's default editor, but that's wrong; it always defaults
to RTF, regardless of the user's setting. There is no way to change
it to Plain Text outside the user interface. In Internet Mail Only
mode, this is a potentially serious problem, because it means that
messages in Rich Text format may go out to any recipient not
specifically marked "Send with Plain Text."
One workaround (thanks to MVP Ken Slovak) is to force the message
to HTML using this code:
objItem.HTMLBody =
"<HTML><BODY>" & objItem.Body &
"</BODY></HTML>"
I think this problem goes back to Outlook 98, but it's worth
noting because people may start using the ItemSend event to do more
things with your average outgoing item.
On the Contact form, the Journal page is renamed
"Activities":
This means that any code that hid or showed the Journal page will
need to be updated.
The Help system is awful:
Not only is the HTML help for Office 2000 difficult to use, slow,
and lacking in bookmark capability, but it's just plain wrong in
many cases. Some of the sample Outlook code doesn't work, and some
of the examples are inappropriate. Don't bet the farm on anything
you read in the Help system. Test it yourself.
The Registry key for the Master Category list has moved:
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 2000. 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 is in the
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Categories
key -- not in the default value but in the MasterList value. |
