A
AndThat
Using OL2002
I made a custom contact form called IPM.Contact.MyForm. I changed the
message class of all the existing items in my folder, which is a sub-folder
of the main Contacts folder, by using the omsgclas.doc macro that I found on
slipstick.com. I also made "MyForm" the default form for that folder in its
Properties.
I view my items in this folder in a modified "Phone List" view and they are
grouped by a custom field called "Frequency." When I need to change the
value in the "Frequency" field, I've found that I can simply highlight the
item row and drag it down into the new grouping and that changes the value
in the field. This is very convenient.
The problem is that when I do this, the Message Class for that item reverts
to IPM.Contact. The custom form remains with my design etc. but the message
class says that it's the default form . This is screwing up certain rules
and macros I've written.
Can anyone help me understand why this is happening and how to prevent it?
I made a custom contact form called IPM.Contact.MyForm. I changed the
message class of all the existing items in my folder, which is a sub-folder
of the main Contacts folder, by using the omsgclas.doc macro that I found on
slipstick.com. I also made "MyForm" the default form for that folder in its
Properties.
I view my items in this folder in a modified "Phone List" view and they are
grouped by a custom field called "Frequency." When I need to change the
value in the "Frequency" field, I've found that I can simply highlight the
item row and drag it down into the new grouping and that changes the value
in the field. This is very convenient.
The problem is that when I do this, the Message Class for that item reverts
to IPM.Contact. The custom form remains with my design etc. but the message
class says that it's the default form . This is screwing up certain rules
and macros I've written.
Can anyone help me understand why this is happening and how to prevent it?