We have several custom Exchange forms installed in the Organizational Forms
library. The forms have been in use for a couple of years with no problems.
However, we are now seeing problems with some users with Outlook 2003 running
in Cached Exchange Mode. When these users click on the saved .oft file, a
blank message form is opened rather than the form. Disabling cached mode
resolves the problem, but laptop users really need the cached mode.

I have confirmed that 'synchronize forms' is checked in the 'send/receive'
properties box, and I cleared the forms cache with no change. Does anyone
know what else I can check?

Thanks,
Joe

The synchronize forms setting is for published forms. It's irrelevant to ..oft files, which generally should not be used anyway. Beginning with Outlook 2003 SP2, users can work with most .oft form templates files only by opening the template from the Tools | Forms | Choose Form dialog, browsing for User Templates in File System. This means that if the .oft file is sent as a message attachment, the user must save it to the local hard drive first.

The article at http://support.microsoft.com/?id=907985 explains this change in more detail, suggests best practices, and provides registry keys that can return Outlook 2003 to the older, less secure behavior.

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


"Joe" <(E-Mail Removed)> wrote in message news:EF20D7C5-B6AC-4C0F-9CCA-(E-Mail Removed)...
> We have several custom Exchange forms installed in the Organizational Forms
> library. The forms have been in use for a couple of years with no problems.
> However, we are now seeing problems with some users with Outlook 2003 running
> in Cached Exchange Mode. When these users click on the saved .oft file, a
> blank message form is opened rather than the form. Disabling cached mode
> resolves the problem, but laptop users really need the cached mode.
>
> I have confirmed that 'synchronize forms' is checked in the 'send/receive'
> properties box, and I cleared the forms cache with no change. Does anyone
> know what else I can check?
>
> Thanks,
> Joe

Sue,
Thanks. Great response. I will look at your links today.

Joe

"Sue Mosher [MVP-Outlook]" wrote:

> The synchronize forms setting is for published forms. It's irrelevant to ..oft files, which generally should not be used anyway. Beginning with Outlook 2003 SP2, users can work with most .oft form templates files only by opening the template from the Tools | Forms | Choose Form dialog, browsing for User Templates in File System. This means that if the .oft file is sent as a message attachment, the user must save it to the local hard drive first.
>
> The article at http://support.microsoft.com/?id=907985 explains this change in more detail, suggests best practices, and provides registry keys that can return Outlook 2003 to the older, less secure behavior.
>
> --
> Sue Mosher, Outlook MVP
> Author of Microsoft Outlook 2007 Programming:
> Jumpstart for Power Users and Administrators
> http://www.outlookcode.com/article.aspx?id=54
>
>
> "Joe" <(E-Mail Removed)> wrote in message news:EF20D7C5-B6AC-4C0F-9CCA-(E-Mail Removed)...
> > We have several custom Exchange forms installed in the Organizational Forms
> > library. The forms have been in use for a couple of years with no problems.
> > However, we are now seeing problems with some users with Outlook 2003 running
> > in Cached Exchange Mode. When these users click on the saved .oft file, a
> > blank message form is opened rather than the form. Disabling cached mode
> > resolves the problem, but laptop users really need the cached mode.
> >
> > I have confirmed that 'synchronize forms' is checked in the 'send/receive'
> > properties box, and I cleared the forms cache with no change. Does anyone
> > know what else I can check?
> >
> > Thanks,
> > Joe
>

Sue,
I've read through the link you sent. I understand the issues with send .oft
files. I actually have the custom form published in the Organization forms
library as described in the article. However, the QA department has been
sending a link to the .oft file to individual users so they can open the
correct form and enter data. Is there a way to send a link to a published
form so the .oft file is not required?

Thanks,
Joe

"Sue Mosher [MVP-Outlook]" wrote:

> The synchronize forms setting is for published forms. It's irrelevant to ..oft files, which generally should not be used anyway. Beginning with Outlook 2003 SP2, users can work with most .oft form templates files only by opening the template from the Tools | Forms | Choose Form dialog, browsing for User Templates in File System. This means that if the .oft file is sent as a message attachment, the user must save it to the local hard drive first.
>
> The article at http://support.microsoft.com/?id=907985 explains this change in more detail, suggests best practices, and provides registry keys that can return Outlook 2003 to the older, less secure behavior.
>
> --
> Sue Mosher, Outlook MVP
> Author of Microsoft Outlook 2007 Programming:
> Jumpstart for Power Users and Administrators
> http://www.outlookcode.com/article.aspx?id=54
>
>
> "Joe" <(E-Mail Removed)> wrote in message news:EF20D7C5-B6AC-4C0F-9CCA-(E-Mail Removed)...
> > We have several custom Exchange forms installed in the Organizational Forms
> > library. The forms have been in use for a couple of years with no problems.
> > However, we are now seeing problems with some users with Outlook 2003 running
> > in Cached Exchange Mode. When these users click on the saved .oft file, a
> > blank message form is opened rather than the form. Disabling cached mode
> > resolves the problem, but laptop users really need the cached mode.
> >
> > I have confirmed that 'synchronize forms' is checked in the 'send/receive'
> > properties box, and I cleared the forms cache with no change. Does anyone
> > know what else I can check?
> >
> > Thanks,
> > Joe
>

No, there is no way for a hyperlink itself to create a new item using a custom form. You can, however, use an item created from form launcher form in a public folder to launch a custom form. See http://www.outlookcode.com/d/forms/formlauncher.htm

Or, put code in a web page; see http://www.outlookcode.com/d/code/formonweb.htm

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


"Joe" <(E-Mail Removed)> wrote in message news:12D66025-A26F-47B0-A102-(E-Mail Removed)...
> Sue,
> I've read through the link you sent. I understand the issues with send .oft
> files. I actually have the custom form published in the Organization forms
> library as described in the article. However, the QA department has been
> sending a link to the .oft file to individual users so they can open the
> correct form and enter data. Is there a way to send a link to a published
> form so the .oft file is not required?
>
> Thanks,
> Joe
>
> "Sue Mosher [MVP-Outlook]" wrote:
>
>> The synchronize forms setting is for published forms. It's irrelevant to ..oft files, which generally should not be used anyway. Beginning with Outlook 2003 SP2, users can work with most .oft form templates files only by opening the template from the Tools | Forms | Choose Form dialog, browsing for User Templates in File System. This means that if the .oft file is sent as a message attachment, the user must save it to the local hard drive first.
>>
>> The article at http://support.microsoft.com/?id=907985 explains this change in more detail, suggests best practices, and provides registry keys that can return Outlook 2003 to the older, less secure behavior.
>>
>> --
>> Sue Mosher, Outlook MVP
>> Author of Microsoft Outlook 2007 Programming:
>> Jumpstart for Power Users and Administrators
>> http://www.outlookcode.com/article.aspx?id=54
>>
>>
>> "Joe" <(E-Mail Removed)> wrote in message news:EF20D7C5-B6AC-4C0F-9CCA-(E-Mail Removed)...
>> > We have several custom Exchange forms installed in the Organizational Forms
>> > library. The forms have been in use for a couple of years with no problems.
>> > However, we are now seeing problems with some users with Outlook 2003 running
>> > in Cached Exchange Mode. When these users click on the saved .oft file, a
>> > blank message form is opened rather than the form. Disabling cached mode
>> > resolves the problem, but laptop users really need the cached mode.
>> >
>> > I have confirmed that 'synchronize forms' is checked in the 'send/receive'
>> > properties box, and I cleared the forms cache with no change. Does anyone
>> > know what else I can check?
>> >
>> > Thanks,
>> > Joe
>>

Thanks again Sue.

Joe

"Sue Mosher [MVP-Outlook]" wrote:

> No, there is no way for a hyperlink itself to create a new item using a custom form. You can, however, use an item created from form launcher form in a public folder to launch a custom form. See http://www.outlookcode.com/d/forms/formlauncher.htm
>
> Or, put code in a web page; see http://www.outlookcode.com/d/code/formonweb.htm
>
> --
> Sue Mosher, Outlook MVP
> Author of Microsoft Outlook 2007 Programming:
> Jumpstart for Power Users and Administrators
> http://www.outlookcode.com/article.aspx?id=54
>
>
> "Joe" <(E-Mail Removed)> wrote in message news:12D66025-A26F-47B0-A102-(E-Mail Removed)...
> > Sue,
> > I've read through the link you sent. I understand the issues with send .oft
> > files. I actually have the custom form published in the Organization forms
> > library as described in the article. However, the QA department has been
> > sending a link to the .oft file to individual users so they can open the
> > correct form and enter data. Is there a way to send a link to a published
> > form so the .oft file is not required?
> >
> > Thanks,
> > Joe
> >
> > "Sue Mosher [MVP-Outlook]" wrote:
> >
> >> The synchronize forms setting is for published forms. It's irrelevant to ..oft files, which generally should not be used anyway. Beginning with Outlook 2003 SP2, users can work with most .oft form templates files only by opening the template from the Tools | Forms | Choose Form dialog, browsing for User Templates in File System. This means that if the .oft file is sent as a message attachment, the user must save it to the local hard drive first.
> >>
> >> The article at http://support.microsoft.com/?id=907985 explains this change in more detail, suggests best practices, and provides registry keys that can return Outlook 2003 to the older, less secure behavior.
> >>
> >> --
> >> Sue Mosher, Outlook MVP
> >> Author of Microsoft Outlook 2007 Programming:
> >> Jumpstart for Power Users and Administrators
> >> http://www.outlookcode.com/article.aspx?id=54
> >>
> >>
> >> "Joe" <(E-Mail Removed)> wrote in message news:EF20D7C5-B6AC-4C0F-9CCA-(E-Mail Removed)...
> >> > We have several custom Exchange forms installed in the Organizational Forms
> >> > library. The forms have been in use for a couple of years with no problems.
> >> > However, we are now seeing problems with some users with Outlook 2003 running
> >> > in Cached Exchange Mode. When these users click on the saved .oft file, a
> >> > blank message form is opened rather than the form. Disabling cached mode
> >> > resolves the problem, but laptop users really need the cached mode.
> >> >
> >> > I have confirmed that 'synchronize forms' is checked in the 'send/receive'
> >> > properties box, and I cleared the forms cache with no change. Does anyone
> >> > know what else I can check?
> >> >
> >> > Thanks,
> >> > Joe
> >>
>