G
General Padding
I have a .oft form which my users open by clicking a link on our
intranet. The form is also published in the Organizational Form
Library, but people primarily use the .oft file. We are using Exchange
2000 with Outlook 2000 sp2 (with the security enhancements). Windows
2000 domain, roaming profiles.
The form is a vacation request form, borrowing heavily from Sue's
example in her Microsoft Outlook Programming book (Buy it if haven't
already). Most machines operate as I expect. The user opens the .oft,
they get prompted to Enable/Disable macros, they choose "enable". Then
they fill out the form and send it. Some machines do not get prompted,
and as a result, don't run the code that generates the Approval form.
In these case, the manager gets the form and approves it, but none of
the information is included and the form does not get CC'd to HR for
their record keeping.
Sometimes the employee gets prompted to enable, and does everything they
should, but the manager doesn't get prompted, which also exists as a
point of failure.
Now this seems limited to a few machines. The same user can log in
elsewhere and have no problems. On problem machines, the same behavior
occurs whether the .oft is used, or the form is opened via the OFL. So
it seems that there is a problem with the settings on some of the
clients, but nothing looks to be different, pending a more thorough
investigation this morning.
Is it possible for OL2K to think a form has been one-offed if it hasn't?
intranet. The form is also published in the Organizational Form
Library, but people primarily use the .oft file. We are using Exchange
2000 with Outlook 2000 sp2 (with the security enhancements). Windows
2000 domain, roaming profiles.
The form is a vacation request form, borrowing heavily from Sue's
example in her Microsoft Outlook Programming book (Buy it if haven't
already). Most machines operate as I expect. The user opens the .oft,
they get prompted to Enable/Disable macros, they choose "enable". Then
they fill out the form and send it. Some machines do not get prompted,
and as a result, don't run the code that generates the Approval form.
In these case, the manager gets the form and approves it, but none of
the information is included and the form does not get CC'd to HR for
their record keeping.
Sometimes the employee gets prompted to enable, and does everything they
should, but the manager doesn't get prompted, which also exists as a
point of failure.
Now this seems limited to a few machines. The same user can log in
elsewhere and have no problems. On problem machines, the same behavior
occurs whether the .oft is used, or the form is opened via the OFL. So
it seems that there is a problem with the settings on some of the
clients, but nothing looks to be different, pending a more thorough
investigation this morning.
Is it possible for OL2K to think a form has been one-offed if it hasn't?