View Single Post
  #7  
Old July 16th 07, 04:24 PM posted to microsoft.public.outlook
Ade_kcc
external usenet poster
 
Posts: 5
Default Outlook 2003 custom form fields not accessible to Exchange Server

On Jul 11, 1:43 pm, "Sue Mosher [MVP-Outlook]"
wrote:
That article actually deals with a different issue -- the addition of the user's signature to a new item created with a custom form. I understood your issue to be the addition of the designer's signature to the form itself.

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

"Ade_kcc" wrote in ooglegroups.com...
Very true it's just, as I said, that as the creator of organisational
forms it just seems odd that the development function, for the
organisaton, is subject to the same rules as the user function.


It seems that this issue, of unwanted signatures, is recognised and
Microsoft have issued a fix, for one situation anyway, which does
actually help in this scenario where I want to prevent signatures
being added to the form message. :-)


http://content.techrepublic.com.com/...1-36647-3.html


On Jul 6, 2:30 pm, "Sue Mosher [MVP-Outlook]"
wrote:
There's nothing to "fix" regarding the signature. If you don't want the signature to appear, you turn it off. If you do want it, you turn it on. Since you don't want it to appear when designing forms, you turn it off.


"Ade_kcc" wrote in glegroups.com...


I also then have the problem that if I set a
default signature block my sig is built-in to the published form and
appended to all messages sent using that form by other users!!- Hide quoted text -


You are, of course, right Sue. It is a different issue, but to this
newbie they seem related.

I fear that you and I will never agree on whether the signature
default in design mode is a 'problem' or a 'feature' :-)

Ads