Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Section Access;
LOAD * INLINE [
ACCESS, USERID, PASSWORD, REGION
ADMIN, ADMIN, ADMIN,
USER, USER1, U1, AFRICA
USER, USER2, U2, AMERICA
USER, USER3, U3, ASIA
USER, USER4, U4, EUROPE
USER, USER5, U4, AMERICA
USER, USER5, U5, *
];
Section Application;
SALES:
LOAD * INLINE [ I WANT KNOW EXPLINATION OF THIS OR WHAT IS CAUSE TO WRITE SECTION APPLICATION TABLE HERE AND ITS MANDATORY?
REGION, PROFIT
AFRICA, 1000
AMERICA, 2000
ASIA, 3000
EUROPE, 4000
OCEANIA, 5000
];
Hi,
Section Access; // means that following comes the security table with users, roles, reduction fields and omitted columns
...
Section Application; // means that the security table has been already loaded, and following comes the normal script and the data model.
Both of them are mandatory if you are using section access.
Miguel
yes, is mandatory because there is a section access before that
from online help
section (access | application)
"
With the section statement, it is possible to define whether the subsequent Load and Select (SQL) statements should be considered as data or as a definition of the access rights.
The syntax is:
section (access | application)
Examples:
Section access;
AuthorizationTable:
SQL SELECT ACCESS, NTNAME, REGION FROM AuthorizationTable ;
Section application;
If nothing is specified, section application is assumed. The section definition is valid until a new section statement is made.
"
Hi
Section access and section application are Indicator of begining and end of code for security
without them security or access can not be fullfilled.
try without any of them an see the result.
hope this helps
Please also have a look at