Forms breaking automatic rules?

R

Rajesh K

Hi,
I created a form based off "New Message.oft" and used it outlook 2003. I
found out that when I used the derived form instead of the original form, the
following things break:

1. Rules that auto-forward broken: these rules do not. i.e., if I create
a rule that automatically forwards some of the email received in the inbox,
the rule does not fire.

2. Blue forwarded arrow missing. When I manually forward an email, the
inspector says that the email has been forwarded but the blue arrow icon on
the exporer is missing.

Any ideas what is going on? My customers need to know.

I do have a tiny amount of vb cpode in the forms.

RK
 
S

Sue Mosher [MVP-Outlook]

I presume you published this form and are not creating items from the ..oft file. (Code runs only on published forms.)

1) Don't know why what would happen. Might not be related to the form at all.

2) Sounds perfectly normal. Custom form items can show only one icon, the one set on the (Properties) page.
 
R

Rajesh K

Hi Sue,

I do publish the form. My form is named MyNewMessage.oft. The steps I
take are:

1. Set HKCU\Software\Microsoft\Office\[version]\Outlook\Custom
Forms\Compose , IPM.Note = IPM.Note.MyNewMessage

2. I then publish the form calling MyPublishForm [code shown at the end].

3. Set HKLM\Software\Microsoft\Office\[version]\Outlook\, value of
ForceFormReload = 1

That should do it, I guess ...

Any ideas ?

Thanks
RK
Code for publishing a form:

DWORD __stdcall MyPublishForm(LPSTR pszFormFileName, LPSTR pszName)
{
DWORD dwStatus;
Outlook::_ApplicationPtr spApp("Outlook.Application");

if (spApp == NULL)
{
return -1;
}
Outlook::_NameSpacePtr pMAPI = spApp->GetNamespace("MAPI");

if (pMAPI == NULL)
return -1;

dwStatus = pMAPI->Logon("","",false,false);

if (dwStatus != 0)
return dwStatus;

Outlook::_MailItemPtr pItem =
spApp->CreateItemFromTemplate(pszFormFileName, vtMissing);

if (pItem == NULL)
return -1;

Outlook::FormDescriptionPtr pFormDescr = pItem->FormDescription;

pFormDescr->Name= pszName;

dwStatus = pFormDescr->PublishForm(Outlook::eek:lPersonalRegistry, vtMissing);

return dwStatus;
}
=== Code end.
 
S

Sue Mosher [MVP-Outlook]

Using a published custom form as the default form for new messages is a very bad idea, all the way around. I don't know if that's related to the rules problem, but I would strongly suggest that you consider other solutions to whatever it is you're trying to accomplish with that custom form.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


Rajesh K said:
Hi Sue,

I do publish the form. My form is named MyNewMessage.oft. The steps I
take are:

1. Set HKCU\Software\Microsoft\Office\[version]\Outlook\Custom
Forms\Compose , IPM.Note = IPM.Note.MyNewMessage

2. I then publish the form calling MyPublishForm [code shown at the end].

3. Set HKLM\Software\Microsoft\Office\[version]\Outlook\, value of
ForceFormReload = 1

That should do it, I guess ...

Any ideas ?

Thanks
RK
Code for publishing a form:

DWORD __stdcall MyPublishForm(LPSTR pszFormFileName, LPSTR pszName)
{
DWORD dwStatus;
Outlook::_ApplicationPtr spApp("Outlook.Application");

if (spApp == NULL)
{
return -1;
}
Outlook::_NameSpacePtr pMAPI = spApp->GetNamespace("MAPI");

if (pMAPI == NULL)
return -1;

dwStatus = pMAPI->Logon("","",false,false);

if (dwStatus != 0)
return dwStatus;

Outlook::_MailItemPtr pItem =
spApp->CreateItemFromTemplate(pszFormFileName, vtMissing);

if (pItem == NULL)
return -1;

Outlook::FormDescriptionPtr pFormDescr = pItem->FormDescription;

pFormDescr->Name= pszName;

dwStatus = pFormDescr->PublishForm(Outlook::eek:lPersonalRegistry, vtMissing);

return dwStatus;
}
=== Code end.

Sue Mosher said:
I presume you published this form and are not creating items from the ...oft file. (Code runs only on published forms.)

1) Don't know why what would happen. Might not be related to the form at all.

2) Sounds perfectly normal. Custom form items can show only one icon, the one set on the (Properties) page.
Click to expand...
Click to expand...
 
R

Rajesh K

Agreed. I am using "other mechanisms" O2K7. In the older versions there were
interaction issues with other companies' addins and toolbars and we had
customers complain about it. Being the smaller vendor, we were forced to use
the suboptimal forms method for pre-o2k7. It works beautifully for most
customers ... Except for the two issues :(

Sigh ..
Rajesh

Sue Mosher said:
Using a published custom form as the default form for new messages is a very bad idea, all the way around. I don't know if that's related to the rules problem, but I would strongly suggest that you consider other solutions to whatever it is you're trying to accomplish with that custom form.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


Rajesh K said:
Hi Sue,

I do publish the form. My form is named MyNewMessage.oft. The steps I
take are:

1. Set HKCU\Software\Microsoft\Office\[version]\Outlook\Custom
Forms\Compose , IPM.Note = IPM.Note.MyNewMessage

2. I then publish the form calling MyPublishForm [code shown at the end].

3. Set HKLM\Software\Microsoft\Office\[version]\Outlook\, value of
ForceFormReload = 1

That should do it, I guess ...

Any ideas ?

Thanks
RK
Code for publishing a form:

DWORD __stdcall MyPublishForm(LPSTR pszFormFileName, LPSTR pszName)
{
DWORD dwStatus;
Outlook::_ApplicationPtr spApp("Outlook.Application");

if (spApp == NULL)
{
return -1;
}
Outlook::_NameSpacePtr pMAPI = spApp->GetNamespace("MAPI");

if (pMAPI == NULL)
return -1;

dwStatus = pMAPI->Logon("","",false,false);

if (dwStatus != 0)
return dwStatus;

Outlook::_MailItemPtr pItem =
spApp->CreateItemFromTemplate(pszFormFileName, vtMissing);

if (pItem == NULL)
return -1;

Outlook::FormDescriptionPtr pFormDescr = pItem->FormDescription;

pFormDescr->Name= pszName;

dwStatus = pFormDescr->PublishForm(Outlook::eek:lPersonalRegistry, vtMissing);

return dwStatus;
}
=== Code end.

Sue Mosher said:
I presume you published this form and are not creating items from the ...oft file. (Code runs only on published forms.)

1) Don't know why what would happen. Might not be related to the form at all.

2) Sounds perfectly normal. Custom form items can show only one icon, the one set on the (Properties) page.

Hi,
I created a form based off "New Message.oft" and used it outlook 2003. I
found out that when I used the derived form instead of the original form, the
following things break:

1. Rules that auto-forward broken: these rules do not. i.e., if I create
a rule that automatically forwards some of the email received in the inbox,
the rule does not fire.

2. Blue forwarded arrow missing. When I manually forward an email, the
inspector says that the email has been forwarded but the blue arrow icon on
the exporer is missing.

Any ideas what is going on? My customers need to know.

I do have a tiny amount of vb cpode in the forms.

RK
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Create a rule that acts on received auto-forwarded messages 4
Send link to item using Folder Assistant rule 6
Forward Email Rule Not Working Automatically 6
Rules don't fire automatically in Outlook 2007 7
automatic email forwarding rule 2
Auto-forward email using custom form. 0
Second mailbox rules 1
Create a rule to automatically forward calendar items when saved 2

Top