Hi Everyone,
We are having an issue with service pack 3 shutting down scripting behind
our Outlook forms and I am trying to find a solution.

Our forms work correctly from where they are published in a public folder
but once submitted the scripting is shut down at the next step in the work
flow.  The next person to open the form is unable to use any of the scripted
buttons.  I can partially fix this by setting the form not to send it's
definition with the message so it will load from the original published
trusted form but then we run into the next problem.
The 2nd step in the application workflow is for a person from a different
group to make their changes/additions to the form and then FORWARD the form
to the next group.  The forward action does not allow you to select a form
object in a public folder, only one in the Organizational Forms Library.

My dilema is that the company is pushing SP3 to all desktops in the near
future and many of our Outlook forms will stop functioning.
I do not have access to publish to the Organizational Forms Library and if I
were to get access to it there are several other issues such as changes to
the workflow for the clients.  I do not know where the forms library is
located and I assume that by publishing there all clients will have to then
launch the forms from a different location than they are used to or I will
have to keep two versions of the forms up to date, one in the original
public folder and a second with a varied name in the organizational library
so the content will always have a trusted form to load it's data into and
prevent it from shutting down scripting.

Is there an easier solution than drastic rewrites to all of the Outlook
forms?  I read about Administrative Options for the Outlook E-mail Security
Update on Slipstick.com and although vague about how it might apply to
Outlook forms it sounds like it might work but then we have to deal with the
Exchange Server teams to install and configure the administrative form, then
the Desktop Engineering folks to review and approve the registry changes and
potentially push them to clients and then with the Information Security to
decide if they will allow the changing of default security options in
Outlook and to add clients into the groups.  The whole process will be a
headache and very time consuming in our 5 meeting per decision environment
(possible exaggeration but you know how it gets).

Any easier methods of getting my apps working without having to have admin
access on the exchange servers and individual PCs or trying to get those
groups to cooperate?

Help!!!!

Trent

P.S.  Sorry for crossposting but all of these groups seem to be valid
locations for this type of question.