I thought the behaviour I experienced (described in two posts back) seemed
to indicate that the registry fix did more than just allow the custom form
to display in the Preview Pane. When the registry fix was in place, the
Post Item that would otherwise display in the custom form did then display
in the Preview Pane, but it also reverted to opening in the regular Post
Item form (when it was opened) and, perhaps as might be expected, in the
regular Post Item form when then being revised. In other words, the
registry fix seemed to be having the effect of saying, if an item is
supposed to be opened and revised in the custom form, then override that
setting and preview, open and revise it in the regular form instead - ie the
registry fix does not just cause the Post Item to be displayed it in the
Preview Pane. I interpreted that as meaning that the registry fix was
overriding the MessageClass property since that property (as I understand
it) forces the Post Item to be opened and revised in the custom form. This
does seem odd because the registry fix implies it would only affect the
preview behaviour (since the new string value is in the Preview key).

In one sense, it doesn't matter too much because (as I understand it)
whichever route I take, I cannot get the behaviour I want from Outlook
2002 - which is to be able to preview, open and edit a Post Item using a
custom form.

Best regards
Geoff




"Sue Mosher [MVP-Outlook]" wrote in message
...
I don't think the registry fix has anything to do with the message class. It
just allows custom forms to show in the preview pane.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Geoff" wrote in message
...
Very many thanks for seeing me through this.

On reflection after my last post, I felt that the registry fix wasn't
appropriate. In effect, it seems the registry fix overrides the Post
Item's
MessageClass property (if that has been set to display the Post Item in a
custom form) so that the Post Item displays in the regular form. The
(rhetorical) question then arises, why bother to set the MessageClass
property in the first place?