In an earlier post I wrote about how to authorize the script Execute statement and the differences between QlikView versions 11 and 12. I’ve just tested the new QlikView v12.10 Initial Release and the rules have changed again.
To run an Execute statement in QV12 Desktop requires that “User Preference, Security, Script (Allow Database Write and Execute Statements)” be checked on. This is also true in QV12.10.
An additional Script Setting “Can Execute External Programs” is present in QV12 but had no effect. In QV12.10, this setting behaves as it does in QV11. If off, you will be asked to authorize when the Execute statement is encountered in the script.
For an Execute to run in QV12.10 Desktop without prompting, both “Script (Allow Database Write and Execute Statements)” and “Can Execute External Programs” must be on.
What about QV12.10 Server? Like QV12 Server, Execute is authorized by the setting:
The value is set in “C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch\settings.ini”, and it is off by default after install.
Does QV12.10 Server need the “Can Execute External Programs” setting? No. As a matter of fact, if it’s off, the reload sets it on. I don’t mean temporarily. I mean it sets and saves it in the qvw.
What is the intent behind this QV12.10 change? I’m not sure.