topic How to get the Macro-security dialog back in QlikView

How to get the Macro-security dialog back

jerrysvensson — Mon, 26 Jan 2026 18:19:17 GMT

QV Version 10 sr2 and sr3

A customer has done the incorrect choice allowing macros when opening the document. How do I get the dialog back so that they can choose the correct one?

He and also I (testing this on our own server) has no entry :HKCU\Software\QlikTech\QlikOcx\Settings for Qlikview Servers in the Registry. Ctrl + Shift+M shows the dialog in Plugin but we can't have the users do that all the time..

How to get the Macro-security dialog back

fosuzuki — Fri, 02 Sep 2011 10:32:27 GMT

Hi,

I found out that in Win7+QV10SR2, the config is saved in C:\Users\username\AppData\Roaming\QlikTech\QlikView\Settings.ini.

There should have some entries like:

[Settings for QlikView Servers]

Module Script System\yourserver1=

Module Script System\yourserver2=

[Module Checksums Safe]

E001BD0B-202A5C95-42A7C838-838CBB00-1BE8464C=

[Module Checksums System]

4EA1B472-451015AF-926EE07A-67F7C3B4-376921C1=

I think that the 'Module Checksums' are the checksums for each local qvw. Try deleting these entries. But please save a backup first...

Hope this helps you

Fernando

How to get the Macro-security dialog back

jerrysvensson — Fri, 02 Sep 2011 10:59:33 GMT

Thanks, I didn't know that. Problems is that the customer is a hospital and changing machine stuff is not allowed.. What works on my machine is to create a new sub in the macro, but no difference on the clients machine.

How to get the Macro-security dialog back

jerrysvensson — Fri, 02 Sep 2011 13:03:19 GMT

What works is to change the macro. The clients machine we tested this on was the only one that didn't work out of a 100. A problem with his machine, all others worked..

How to get the Macro-security dialog back

fosuzuki — Fri, 02 Sep 2011 14:04:57 GMT

Maybe the plugin is older version?

How to get the Macro-security dialog back

jerrysvensson — Fri, 02 Sep 2011 14:19:57 GMT

No the problem was that he had an old setting (previous plugin) that collided with the new version 10.