When implementing security at the document, as far as I have known, there can only be two parts - each of which defined only once:
1. Section Access : This statement tells the QVW to look up for security credentials while opening the application.
2. Section Application:
When you define the Section Application statement, you are telling the application to treat everything following this statement as one block of code. This block of code is then dependent on Section Access for security. So, it is not logically possible to break this block of code into two such that each block has its own Section Access and Section Application statements in a single QlikView document, unless community experts think and know otherwise.
This approach would only work if you could break this (like using an unqualify statement after a qualify) but then it does not seem to be a possibility.
Hope that helps.
I don’t think you can have multiple instances of Section Access scripts within your application. However, you can concatenate your new access request to your original Section Access code. You can use a simple Concatenate Load.
Hi Everyone, thanks for your help.
As a result to the answers I have received, I have decided to rethink about where the Section Access is Applied to, and at what level. It's taken a bit of brain scratching, but I have got there in the end. Many thanks again to you both who have taken the time to reply,
A little advice for anyone reading this post - Section Access can be very cool, but take the time to think about how you want your data to be viewed and by whom, it's a bit of a pain to unravel it once you have got it up and running!