Manage Password

Hi All Programming Lovers..

This is my First post...

I have made a ACCOUNT system. In it I have in Main Menu Window or Menu Main Items like FORM, REPORTS, UTILITY and so on. And in these
and i also others Forms like in FORMS:

* ACCOUNT HEADS FILE
* PAYMENT VOUCHERS
* RECEIPT VOUCHERS
* JOURNAL VOUCHERS and so on

and i made them differents tables depends on my needs and as well i made a table named PASSUSR for users passwords stored in it.

My QUESTION IS:
~~~~~~~~~~~~~~~
* How / What should be the structure of this PASSUSR table as i want
to save USERID, PASSWD in it and RIGHTS of different uesrs like
there is 3 users one for MANAGER and second for Assistant of Manager
and third for Operator.

Manager can do all the things where as Assistant can do little and
Operator can do only Data Entery. as i can change there rights of
using of Forms + Report + Utility by changing columns value of PASSUSR.

HOW CAN I ACHIEVE THIS... ???
THANKS

ANY BETTER SUGESTION PLZ... thanks in advance...
bye
from TuM

You can create 'roles' in Oracle corresponding to the types of job viz.,Manager, Asst Manager and Operator.
Then you can code for granting the said role to the user as soon as any new user is created.

there is any way to achieve this without role making...

if you plz. tell me
thanks in advance

any body else...

If you don't want to use database roles, then you need to write logic for this.. Based on the user login, you can populate Menus in the application which call respective forms or reports..

F.ex: Manager will get to see all accounting reports or summary reports whereas Operators will able to see only general reports..

I suggest that TuM familiarizes himself with the logic of Oracle Priviliges and Roles. It might provide a good example for a design for a customized system.

Quote:

---

Originally posted by dknight
I suggest that TuM familiarizes himself with the logic of Oracle Priviliges and Roles. It might provide a good example for a design for a customized system.

---

Though I talked about writting program logic, I support David's suggestion.. Much better than coding privileges in programs..