I am hoping to use the DisableCommand feature to stop my users editing some QA based Rules we are implementing onto everyone’s mailboxes. Since I can’t disable the edit on just one rule I am going to knock out the editor completely (brutal but necessary)
I have tried using the Groupwise.DisableCommand call for 66 (About) and 62 (Rules?) but it doesn’t seem to do anything.
I have put the call as …
in an applet that runs on the OnStartup event but I can still access the About dialog.
I have realised I can disable the Rules by having an applet that replaces the RulesListDlg event and then does nothing but display a message indicating rules are off but I’d rather just disable the command.
We have Groupwise 6.5.2
- You must be logged in to reply to this topic.