View Single Post
  #3  
Old January 4th 07, 05:18 PM posted to microsoft.public.outlook.program_forms
Nikolas
external usenet poster
 
Posts: 34
Default priority of form regions against old legacy forms

Hi Sue,

Thanks for your response.

We provided our customers an addin for Outlook 2003 that was involving
having the old forms in their organizational or personal folder. Now we want
them to upgrade to the new Outlook '07 addin that involves form regions. We
could delete the forms in the personal folder but not the forms in
organizational folder since not all users will upgrade at the same time. So
we want those that do upgrade to use the form regions and not the forms in
the organizational folder.

The behaviour that we get is that when the user double clicks on an item
(that is associated with our message class) the item uses the old forms (from
the organizational folder). If we close it down and then open it again it
uses the form regions. Also if the user when he just receives an item with
our message class and he just clicks on it without opening it, it won't be
visible in the reading pane (even though we use the showReadingPane to true).
If then selects another item then the previous item changes message class to
the default IPM.Note.

I get the same behaviour if I use replace property or the replaceAll.

"Sue Mosher [MVP-Outlook]" wrote:

Best practice advice from Microsoft is not to mix form regions and a legacy form on the same item. Is your form region using a replaceall region? What kind of weird behavior are you seeing?

--
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

"Nikolas" wrote in message ...
Hi,

Using Outlook '07 and form regions, is it possible to force Outlook to use
the form region instead of the custom legacy form that sits on the personal
folder for the same message class?

Currently we do get some wierd behaviour when opening an item with a custom
message class that is associated with a form region and an old legacy form
that sits on the personal forms folder.


Ads