>>>>> "Robert" == Robert Monical <[EMAIL PROTECTED]> writes:
Robert> Each screen has a defined list of possible actions. This
Robert> information is "hardcoded" into the entry logic for the
Robert> screen. When a screen is sent to the user, the possible
Robert> action is checked and enabled/disabled based on the user
Robert> privilege. The maintenance screen for these tables will be
Robert> in Oracle forms.
I would NOT show all actions that are available in the system but rather
only show the actions which client viewing your actions screen has
access to. In my experience showing all available actions whether
granted to the client or not, tends to give the client 'action envy' and
you will be busy either granting all the actions to the clients they do
not currently have, or explaining why an action is available and they
have not been granted the authority to perform said action.
You can dynamically generate the action list based on the enabled
privileges of a user, and perhaps sock this list into your session
object.
Otherwise, you approach is basic and sound, IMHO.
Peace.
