Problem with one off forms - Help?

[Trent Shirley]

My company is beginning to roll PCs out with Service Pack 3 for Office 2000
and forms are beginning to fail due to the new security.

Here is my problem.
We have a form with a lot of code behind it. The form originally had the
form definition sent with it so once submitted those who opened the form
would not be able to use the built in buttons as the script would not
execute because the form was now one off'd.
This was easy to fix by unchecking the box to send the form definition along
with the posting of the completed form.
Here is where the problem begins. The form gets submitted by one group and
it posts to an Outlook folder. Another group picks up the form, the code is
still working as it is not now one offed, they make their changes and then
click FORWARD. This unfortunately launches it as a new form, it gets one
off'd and then the scripting no longer works.
How can I stop the form from becoming one off'd when they click Forward to
send it to the final area/outlook folder?
Would I have to publish a second copy of the same form in the other folder
and change the code to automatically populate a new instance of the
published form in that folder? It seems like a lot of work and that there
should be a simpler solution I just have not seen yet.

 

[Sue Mosher [MVP]]

Edit the properties for the Forward action to make sure that it points to your published form.
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Trent Shirley]

I tried doing that as I saw info on it on slipstick.com but I do not seem to
have the option.
I can only choose between personal forms, standard forms or organizational
forms. I do not have the option to select forms published to folders and do
not have rights to publish organizational forms.

It would be a bit of a battle to get the powers that be to allow publishing
of our forms into Organizational Forms but I would have thought that I
should be able to browse to published forms in exchange folders. It sets
the message class to IPM.Note by default and I cannot change it.


Edit the properties for the Forward action to make sure that it points to
your published form.
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Sue Mosher [MVP]]

Unless you specify your custom form in the Forward action, you'll always get a one-off when you forward an item created with your custom form. Would your application make sense if you moved the item with code instead of forwarding it?

--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Trent Shirley]

I may be able to move rather than forward. I have to better understand the
workflow of the groups involved to be certain. I inherited the support on
these forms and am only becoming familiar with them as I try and
troubleshoot these new problems.

Would you know why I am not able to use the Browse button to browse to the
folder with my published form? I have no problems when I publish the forms
themselves so I do not know why I cannot browse to them to change the
Forward behavior.

I thought about using code to alter the message class but I assume that
since the form is generated upon pressing the Forward button that the
scripting is already disabled within the new form and the change to the
message class would not work.

Another option would be to disable Forward and have a submit button that
would create the new form object using the identified form. This is
probably the most involved method though.

Unless you specify your custom form in the Forward action, you'll always get
a one-off when you forward an item created with your custom form. Would your
application make sense if you moved the item with code instead of forwarding
it?

--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Sue Mosher [MVP]]

I presume this is a message form? Since messages are designed to be sent, there's usually no guarantee that a particular public folder will be open when the item is sent (or forwarded). So it doesn't make sense to pull a message form for forwarding from a public folder.

Custom message forms almost always need to be published to the Organizational Form library.

The Submit button method was another solution I was thinking of.