Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi There
I am using QV 8.5.
I am trying to acheive something fairly simple. I want to be able to have full access to the QV model myself. However anyone else opening the model must not be able to do any but interact witht he model.
Is this best acheived through access security or some ducument setting ?
And in either case what is the best way to lock everything except document interaction ? In other words they must not be able to alter the model in any way, but only click and interact with the model.
Thanks.
I would suggest that your clients shuld be using the Analyzer version of QlikView whilst you will be using the Enterprise version.
If you are in a client/server environment then your end users probably should be using the IE Plugin Client or Java Client, this is only set at an analyzer level anyway.
Just as a note, there is another version called the developer version, this doesn't allow access to the data model itself but will allow full control/development of objects within qlikview (creation/modification of charts/tables etc).
Hope this helps.
Access security, definitely. After you have indentified the "anybody else" (at login as USER) you can keep for ADMIN all you want. Using the Document Properties (tab Security, user privileges). Once you have made a pair of tests it is fairly simple.
There is also a second level that allow you to hide the script under a different password, but this is another story.
Flavio
Actually with version 9, that is the current one you can download with no problem, there is no such distinction (at desktop level) - any std package will allow the user to do everything. So I would not confide in the fact that the user cannot do "this and that" when they can with a free download. If you can stop the user from having the actual file with a server distribution the story is different and depends on the client type.
Developer version (desktop) in 8,5 allows everything (I've been using it) included the data model creation and editing.
In my opinion, the only way to be sure is to impose limitation trough security.
Flavio