hi,
Now my mfg. consuitant wants to prevent every user who have been assigned as super users to avoid the pain of authorizing them,to use the parameter menu in the stnd.baan menu tccom00000.now for that i suggested to change the menu structure by removing it from the tc menu.
so can anybody tell me the exact procedure how i can prevent the users from accessing the parameter menu in tc,but allow the instructor to do so.
thnx.

I have thought about this for a while and I can not see how you can do this while your users are super-users. What we did in a case like this was to make the super-users normal users, grant them everything. Then we went in and removed only those session we did not want them to have - in our case mostly tools sessions.

Removing the session from the menu will not really keep them from having access. All they need to know is the session name to run it. So I would make them normal users.

Good Luck!

Mark

mark_h is correct - if the user knows the session number they can choose to enter it through the File / Run Program option on the main menu. But you can turn that off by user - User Management "Call Session by Code" option can be turned off.

To remove access via the menus, which Parameters session are you referring to? There are many...one on each Module's menu. To control access via menu to all parameters sessions, you will need a modified menu for each Module that calls the parameters sessions. Then, a modified Main Menu (tccom00000000) that calls your new custom menus for each module. You then replace the user's Start Up menu (in Maintain Users) to the modified Main Menu. Be sure to do the converts all over the place.

Also, then, they have access to all the tools sessions, I assume. They would still be able to go into Maintain Sessions, look up the session, and run it that way. You can control that by menu too I guess, since you are in there modifying all the menus.

All of this still does not take into account any zooms that are in place to go to those sessions, or, if they really know what they are doing, they can modify their menu quickly and get to them anyway.

So, it sure is a lot of work. Seems easier to do it the "normal user" way as Mark suggests.

May not be your exact scenario ... we look to restrict super users from changing those specific parm values which may have catastrophic result.

For the related few parm sessions, our near-absolute soln is to rename (in unix) the related form object. After we broadcast that the session will be off-limits (and we rename the form object), when the session is subsequently invoked, a fatal error will occur.

On the rare occasion that a parm value requires change, we will reinstate the form to allow the change by appropriate personnel, and then deactivate again.

Bob.

Baan4c0, HPUX11, IFMX