D
Dan Allason
Hi All,
I have a set of custom forms that constitute part of a Public Folder CRM
system. All the forms have a substantial amount of VBScript behind them and
are published to the Organizational Forms library. When the forms are run
(for new items and existing items) on OL2003 on an XP machine, they run
without a hitch. One of the requirements for my system is that our remote
users can access the system via their existing terminal services connections.
On testing the system on Windows 2003 Terminal Services, the code on all the
custom forms does not run (the custom code on the Item_Open event doesn't
even fire). Is there some setting on Win2K or Outlook 2003 that would block
the script? The forms are not one-offing (the items all open and run the
script from the XP machines) and the form definition is not being stored with
the item. Any help on this will be greatly appreciated!
Dan
I have a set of custom forms that constitute part of a Public Folder CRM
system. All the forms have a substantial amount of VBScript behind them and
are published to the Organizational Forms library. When the forms are run
(for new items and existing items) on OL2003 on an XP machine, they run
without a hitch. One of the requirements for my system is that our remote
users can access the system via their existing terminal services connections.
On testing the system on Windows 2003 Terminal Services, the code on all the
custom forms does not run (the custom code on the Item_Open event doesn't
even fire). Is there some setting on Win2K or Outlook 2003 that would block
the script? The forms are not one-offing (the items all open and run the
script from the XP machines) and the form definition is not being stored with
the item. Any help on this will be greatly appreciated!
Dan