Vlad

Thanks, I will look into that.

Kev

>Hi!
>
>Programmatically as you define menu items. When you do not have a table for menu items, it is hard to automate it. When you do it programmatically (hardcode each menu item ID or name), it will be harder to support it in the future. SKIP FOR could look like:
>
>SKIP FOR CheckMenuAccess("OrderForm")
>SKIP FOR CheckMenuAccess(MNU_ORDER_FORM)
>
>The last one is a constant defined in the include file, but you will be able to use it only when you have #INCLUDE at top of the MPR file.
>
>>Vlad
>>
>>Time constraints restrict me from carrying out your last solution.
>>
>>I'm aware of the SKIP FOR condition, how can you get the Menu item ID ?
>>
>>Kev
>>>Hi!
>>>
>>>To organize sequrity, you can just add a SKIP FOR condition to each menu item. In that condition you just call a function with menu item ID or name, the function checks if that menu item is available for user and return .T. if not to disable menu item.
>>>
>>>Anyway,
>>>What you meant: user controls access rights, or administrator controls access rights for users?
>>>I have some experiense, but that was quite a complex system with menu built using information in a table that user can adjust (rearrange menu items in trre so they uppear in different submenus). there was also a sequrity table linked to this table that described which items user can see at all, and which items are enabled for user. Menu built on the fly and managed also by form class (this allw as a part of our framework).
>>>
>>>I doubt you will make something like that but...
>>>
>>>
>>>>Hi
>>>>
>>>>Has anyone managed to write anything that allows users of an application to control menu-access rights ?
>>>>
>>>>Thanks
>>>>Kev