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.

"Road Rebel" wrote in message
...
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...;en-us;Q302003


"Hollis Paul" wrote:

In article , Trent wrote:
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.

--
Hollis Paul
Mukilteo, WA USA