Section access in personal edition?

[#1]

I'm wondering if i'm doing anything wrong or if the personal edition is limited in security?

Currently I've a closer look to QVs security:

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD

    ADMIN, adm, adm

    USER, user, user

    USER,test,test

];

Section Application;

Works perfect: Can login with an admin and see all the options, login with a user ends in limited functionality.

But when I add this:

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD

    ADMIN, adm, adm

    USER, user, user

    USER,test,test

];

Section Application;

LOAD * INLINE [

    USERID, NameCountry

    user, Oceania

    test, Nigeria

];

It's no longer possible to login with a user (failed to open document). Any idea?

[Miguel_Angel_Baeyens]

Hi,

Yes, this is one of the quirks in section access scripting. There must be a reduction field, uppercase in the name, that links the section access table that is hidden from the model with the section application area, so for example:

SECTION ACCESS;
// Region is the reduction-link field here
LOAD * INLINE [
ACCESS, USERID, PASSWORD, REGION
ADMIN, ADMIN, ADMIN
USER, USERN, USERN, NORTH
USER, USERS, USERS, SOUTH
];
SECTION APPLICATION;
DATA:
LOAD * INLINE [
REGION, COUNTRY
NORTH, US
NORTH, UK
SOUTH, AR
SOUTH, CL
];

Obviously, as ADMIN you can see all the data.

Hope that makes sense.

Miguel

[kji · Accepted solution]

section access will make all values for USERID (and other "access" specific fields) uppercase, which will break the connection to section application, if you pur the values for USERID in section application in uppercase it should work.

[#4]

Thank you guys!

Works now as expected.

Sadly the hierarchy is not passed by the security, for example:

World

- Europe

- Asia

Section access for World will not pass the access bottom down (but honestly, didn't expected that...).