Is there a way to secure a single script for the end-users. In our situation, a script is needed for some standard reporting and this script should not be changed by the end-users. However, we would like to let the users free to create their own scripts (so we can’t disable working on scripts).
Thanks for any feedback,
Diederik Dellaert
PricewaterhouseCoopers
When a script file is compiled, it creates an *.sbx file with the same name as the *.spt file.
Instead of sending the *.spt file, send the *.sbx file. Users will be able to execute the script, but will not be able to modify it, and they can still create their own custom scripts.