Shallow talk how to build attributive management system effectively

(2) search this post correspondence to be able to use what bill of fare;
(3) the bill of fare that the user can use and system actual menu one by one is compared, screen does not allow the bill of fare that its use;
Because here face involves experience of menu, need uses the use skill of a few PB, detailed sees an article " shallow talk how to use PB to realize trends to add bill of fare " , here no longer give uncecessary details.
Such passing afore-mentioned 3 person relation, build an user to be versed in date can use what bill of fare after all, cannot use what bill of fare. Why to want so complex, why to define every work number what to bill of fare you can use directly? In that way word, apparent system is redundant too big, create resources waste, not up to specification changes a requirement.
2, tiring-room library expresses attributive:
Attributive of tiring-room library watch basically is a basis database of backstage of downstage work number establishs corresponding account (LOGIN) , user (USER) , generate corresponding code according to certain regulation, gift its different role (ROLE) , what different library expresses is different read, write attributive, the tiring-room that uses as a result of this part and place is specific closely related the database, because of this article no longer expatiatory.
3, applied data attributive:
Apply the implementation of data attributive, basically occupy what data logging must introduce among the watch to type through of all kinds number or generation unit code and ID of operator work number, when the user visits corresponding record, compare current user ID to reach its to be in an unit above all, whether with the generation of data logging operator ID and its unit code agree, this problem says simple, but rise actually with PB language implementation need stresses certain skill, want successive ” of “ of sufficient have the aid of this one character, as far as possible efficient, general.