Seperate read and compose form problem

[joebob]

I would like to use two totally separate forms for composing and reading, not "Separate Compose and Read Layouts".

The problem is with the sent messages. Incoming messages use the correct custom read form, messages being composed use the correct custom compose form, but messages that have already been sent are using the *custom compose form* instead of the custom read form.

Is there a way to have it so that once a message gets sent and saved, it opens with the custom read form? I'm not saving the form definition with the form if that makes a difference. This is O2K in C/W mode, SP3, no Exchange Server. Thanks

 

[Sue Mosher [MVP-Outlook]]

Outlook supports separate layouts, not separate forms, unless you use
registry substitution (see
http://www.outlookcode.com/d/newdefaultform.htm#changedefault). I've never
seen a case where a sent message did not use the custom read layout, so this
is a mystery. Maybe you can tell us more about your implementation.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers


I would like to use two totally separate forms for composing and reading,
not "Separate Compose and Read Layouts".

The problem is with the sent messages. Incoming messages use the correct
custom read form, messages being composed use the correct custom compose
form, but messages that have already been sent are using the *custom compose
form* instead of the custom read form.

Is there a way to have it so that once a message gets sent and saved, it
opens with the custom read form? I'm not saving the form definition with
the form if that makes a difference. This is O2K in C/W mode, SP3, no
Exchange Server. Thanks

 

[joebob]

I did in fact use registry substitution via FormSwap.exe but I hadn't
read the fine print about how it affects existing and new items
differently. I will investigate using separate layouts instead. Thanks