You cannot influence section access across documents. You have shown that the original SA survives a binary load and a subsequent SA is ignored. Probably because at script termination time the information in an SA table is moved to a special security zone, and after a binary load QlikView detects that this zone is already taken up and won't fill it a second time.
However, within the same script, you can create SA tables in sequence and each in a different Section Access area. And the most interesting thing is that you can delete the first SA table using a DROP Table statement if you name the first table. Only the last one will be kept.
Didn't know that.
Peter
PS Now Username/password = B/B due to the second Section Access table load.
