It seems that user SEINAXTI doesn't have a valid value for KA1 field, which seems to be the reduction field. Reduction field must have any existing value in the data model so the user can log in and see info. See the following example
SECTION ACCESS; LOAD * INLINE [ ACCESS, USERID, PASSWORD, SALESREP USER, USER1, USER1, A USER, USER2, USER2, B ]; SECTION APPLICATION;// Now all your script...Clients:LOAD CODE,NAME,SALESREP,ADDRESSFROM FILE.QVD (QVD);... // Rest of the script
When is checked "Reduce data based on Section Access" and "Strict Exclusion" in your document properties, Settings menu, On Open tab, you have to make sure that there are records in table "Clients" for that SALESREP value is "B", otherwise USER2, although typing user and password right, will not have access to see info, actually, he cannot login to the document, as there are no possible values for his reduction field SALESREP.
I don't get why you are loading in your sample script "TabA" three times, but I hope this example i useful for what you are looking for.
Thanks for your answer, but it doesn't solve my problem. Let me give more info. The script is only a simplification of a much more complicated and therefore soome things seems unnessesary.
I have some users that only should have access to limitied information in this case SEINAXTI and some users that shall have access to all information SEINTHAN.
The security table in section access looks like this
ACCESS NTNAME NTDOMAINSID KA1
USER SEINAXTI xxxxxx V1
USER SEINTHAN xxxxxx XX
KA1 is the key to the access table in the section application:
The data table contains
A1 A2 A3
V1 V2 V3
X1 X2 X3
According to this SEINAXTI have access to KA1=V1 which should give access to A2=V2 and A3=V3. That is also how it works if you test without section access. But when adding section access the SEINAXTI user doesn't get access to the application.