One off forms problems with Outlook 2003

[Trent]

Hi Everyone,
I have a problem with one off forms running under Outlook 2003.
We had this problem with Outlook 2000 once we went to SP3 and were able to
get around it with the MS Outlook administration form to alter default
security for the clients.
Once we went to Outlook 2003 however all of the forms stopped running again
once they are one-offed. These forms have a workflow to them and have to
submit themselves to other folders where they become non-trusted. Even if
the person's ID is added to the old security form on the exchange server the
code does not execute.

Is there a method specific to Outlook 2003 to alter the default security for
these forms?
I do not have access to the exchange server myself but the folks who do just
keep shaking their heads and saying they have done all the could.
They will not take the responsibility to research the problem and implement
the solution so I have to find the answers and then try to move them into
the fix.

Help?

Thanks.
Trent

 

[Sue Mosher [MVP-Outlook]]

The same method applies in all versions -- the only way to make one-off
items run form code is to use the security settings folder. Why are you
using one-off forms in the first place? That's a sure recipe for problems.

 

[Trent]

Those in charge say they have applied the same settings to everyone and that
it is just not working.
I personally think they set things up incorrectly. It took them a lot of
trial and error to get it working under Outlook 2000 SP3.
They insisted they had set it up correctly and that the problem was on my
end. After twisting their arm several times to get them to try again they
eventually corrected whatever they had not done the first time and it began
working.
I suspect that with 2003 they are making the same initial mistake and
pointing the finger at others rather than reexamining their own work.

The form has to submit to another folder where the next group will perform
the next step in the process.
The company policy prevents us from publishing in the Organizational Forms
Library so that we can just send data and not a copy of the entire form.
Being limited to only publishing in a specific public folder puts us in the
one-off position.

The Desktop Engineering folks SAY they changed default rules to allow code
to execute but I do ont know how they applied that and it obviously does not
work since the forms code does not execute.
What I CAN do is open the submitted copy of the form then select
Tools/Forms/Run Form and then the code will run but this would be very
confusing for the clients who would end up with two copies of the form on
their screen and they may make text changes to the wrong one.

All that I had read said that the process for 2003 was the same for 2000 SP3
except for the registry change needed for 2000.
So I guess they are just doing it wrong and refusing to take responsibility
for addressing the problem. Unfortunately, they have control over it all
and there is nothing I can do directly. *Sigh* I have been fighting this
for just over a year now. I am going to end up rewriting all these forms as
web based applications.