Okay, there are several informative threads on the mechanics of deleting or hiding menu items.

The next level is hiding / deleting items by user group or login.

Thus we want to restrict Sales from accounting functions, etc.

Ideally the restriction levels would be in the MDI frame itself and checked against the user login name but I have no ideas on how to to flag menu items.

This could be stored in a separate table, but this would be cumbersome to say the least whenever a MDI frame is modified.

Any thoughts?

Not sure if I am following your request. If I am you could try this…

During the create event of the MDI frame, you could check if the user is allowed to view or use the menu items. The use the "VISIBLE" property to show or hide each menu item according to the user.

Right, but we still need a database or list of what menu items have what access associated to them.

In ARev we just added a column to the menu table to carry this info and used a custom menu program. Ideally if I could somehow put this info into the individual menu items in the MDI frame, a generic process such as you have suggested would work fine.

AFIAK modifications to the structure of repository items is more or less verboten. The other ques

It isn't perfect but you could associate with the menu name the security level required, say REPORTS_5 would allow anyone with 5 or less to access etc. That way it is already in memory.

FWIW on my most recent project we use a lookup table for this and performance is not negatively impacted.

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Perhaps a tool which could walk the menu to generate new security table entries or delete orphaned ones would make the table driven approach convenient. You would need to run it each time you compiled the menu.

Bob

View this thread on the Works forum...