>Hi Hilmar,
>
>Thank you for your response. We currently have over 300 entries in our menu system. This does not include reports. We would like to keep the menu system as is (if for nothing else, so we don't have a revolt on our hands from our customers)<g>

Well, I can understand that. But perhaps you can manage to advertise the proposed solution as an improvement...

>We have many modules, too many to make a pageframe for each.

Does each and every user have to have access to all 300 entries, or to all modules?

Besides, an alternative to a PageFrame (on the proposed "File | Open" form) might be a ComboBox or ListBox. Each ComboBox item might be for one module, and only the items in the desired module have to be shown at one time.

>I think the idea of a table to hold the entries of the menu is great. I'm just not sure how to dynamically build this menu from the table. I would assume we could do it after the employee logs in...so that we can include or exclude menu options based on security.

While I still prefer a form that lists the entries, I think you should be able to figure out how to place items on a menu, by looking at the code generated by the menu designer.

I am not sure if this will solve the problem about the program too large, but I think it should.

Oh, and another, perhaps more short-term, option might be to split the menu up into two menu programs. There is an option to add a menu to the right of the existing menu system. This might solve your "program too large" problem.