Script behind published form will not execute for some users

[Trent]

We have a custom form published to the Organizational Forms folder and set
NOT to send the form definition.
The form works fine for most of us but we have found some users that the
code will not execute for.
The problem exists the first time they open the form before it is ever even
sent.

One thing we noticed, testing the form on a persons device nearby, when they
opened the form for the first time it gave a message indicating it was
installing the form on the client's machine. Is it somehow pulling this
form down to their computer and thereby turning into a one-off form rather
than executing it from the original location?

And why would this happen to some users and not others?

All clients are using Outlook 2003 and our servers are Exchange 2003. We
have multiple servers in the environment and it is possible the ones having
the problem are connecting through a different server.
We have made sure to clear the forms cache for the client and the
Organizational folder but nothing seems to work.

Any ideas?

 

[Trent]

As an addendum to this problem. We have found that the three people
currently experiencing this issue are all on the same exchange server and
none who it IS working for are on that server.

Any thoughts on possible exchange server settings or issues that could cause
this?

 

[Hollis Paul]

Any thoughts on possible exchange server settings or issues that could cause
this?

This is an Exchange issue, then, and you really should ask in the Exchange
admin group. But, you might ask your exchange administrator if the Org Forms
Library is getting replicated to the other server.

 

[Guest]

Are these users accessing via Terminal Server? By default Office 2003 does
not install the outlvbs.dll when installing on a terminal server. Check this
link:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q302003

 

[Trent]

No terminal server, they connect directly.

The exchange server folks say it is not a server issue.

I created a basic form that just has a msgbox command when it runs to see if
all code was being stopped for them but that form worked.

The server folks want to say the problem is in the code but the code works
perfectly for most people. So if it is code related it may be some command
in the code that may not be properly supported in the clients installation
of Outlook.

When the form loads it populates a select box with a list of approver names.
An approver has to be selected before the form can be sent.
For the users this is failing for the select box never populates which is
what made me think the code is not executing. It is possible that something
in that section of code is failing but we see no errors.

The biggest problem is that the form was created and the problem being
handled by someone else who just comes to me for advice so I am not really
in control of what she does in her testing and she could be making mistakes
or not following my suggestions completely and thereby invalidating the
test.