I would have to see the Section Access load to see what might be the issue. If another user/pw will work and yours will not, then something is wrong with that account. Also, when you login to accesspoint and open a document that has section access applied, everyone is an user even if you have them listed as an administrator.
Here is my script:
LOAD * Inline [
ACCESS, USERID, PASSWORD, HEALTHGOAL
ADMIN, ADMIN, ADMIN,
USER, COACH1, HEALTHY, YES
USER, COACH2, HEALTHY, YES
So I'm trying to reduce the data on load if Coach1 or Coach2 login and Healthgoal = Yes, while still letting me log in as an admin and see all the data.
Perhaps your last sentence is what I need to fix--just list a user that is technically the "admin," but has no value for the data reduction field in the section access script.
Make sure that the field name HEALTHGOAL is same in your data model.
If the name of the field is not same then sure this will not allow you to login.
Also one more thing you must have checked the Strict Exclusion under Opening Tab of Document Properties.
Now when you check that, it will not allow you to login if the FieldName doesnt matches with your data model (Section Application Area)