It should work ok if both documents have the same section access, same username and password. If the access is different or password is different then, of course, you must enter the second set of credentials in order to preserve the security.
If you name the Section Access table you can drop the table after performing the binary load from Doc1 and then load the new Section Access table for Doc2. Something like this:
In all documents you should have the NTNAME field with the DOMAIN\USERNAME form of the user that is running the reload processes (usually the QlikView Administrator, as in Startup, Run, Services.msc, right click on a QlikView Service, Properties, Logon tab) with ADMIN access and able to see all records. Should you need to combine USERID/PASSWORD values with the NTNAME field, check this post with sample working code in this regard.
This will avoid asking for credentials and will remove the original section access and will replace with the one in the binary loader.
Just for clarification: Although this works with normal tables, this will not work if the table has been loaded after the SECTION ACCESS; statement. In other words: you cannot DROP a section access table. Anyway, since the BINARY line is the first to be executed, you always be prompted for credentials to read from the original file if you don't have them already.
On the other hand, the second SECTION ACCESS; (in the binary loader) will overwrite the previous one, so there only will be one security table in place, which always will be the latest loaded.
so you mean that I will have one prompt for the second Section Access?
if Doc1 has Section Access with USERID = user1 and PASSWORD =pass1
and Doc2 has Section Access with USERID = user2 and PASSWORD = pass2 then
if in Doc2 I write Binary Doc1.qvw then I will have only one promt and will be able to access Doc2 using user2 and pss2 and will have both data of both documents?
I have a qvw file with section access . This file is no more refreshed as it is a snapshot of the last financial year ending 31st march 2013. There is a new user who wants access to this file. For the same , I needed to change the Section access script as the user should be able to see data only for a particular region. However refreshing the app would give me up to date data which i dont want.
Hence i decided to take a binary laod and create a section access script in the new file. But that doesnt seem to work and the User is able to view all the regions after i reload the binary script app. i.e the section access from the first application is not getting over written in the new file.
Wondering if I am missing out on something or if there is any other solution to the problem ?
BTW both the binary and the original file have the same document settings. Initial data reduction based on section access is checked in both the files.
.png "Miguel_Angel_Baeyens"){kind=avatar}
