As we discussed last week, with the embedded OCX there is no serial number to associate in section access; but you can use section access and have your OCX application pass in the userid and a “secret” password. If someone tries to open the QVW file with QlikView desktop they will be challenged and asked to enter a valid user and password – which only your application OCX knows.
Thanks for your reply.
I am also counting on the same i.e. secure it with complex user id and password. The only thing that concerns me a little is...All users will have same ID and password.
I have no idea if that is a very safe approach.
I am just trying to find if there is anyway i can have different user id and password for each user but I have not found any way for that yet.
Section access can support multiple users each with a unique userid and password.
But to better secure the QlikView QVW file outside of the OCX application you need to control the password so the user doesn’t take a copy of the QVW file and try to open it with QlikView Desktop or on another QlikView Server get a challenge for a userid and password and simply enter his credentials.
There are several approaches that you can take to do this.