Sounds like a great tool. I would like to take a look at it. Go ahead and email me the print and generated code. Hopefully we can all work together to make this an all inclusive menu system that supports menu objects.

Thanks

>>Since it doesn't look like we are ever going to get one, I am thinking about creating an object oriented menu builder. I am simply looking for feedback to see how everyone would like this. If I get enough positive feedback, I will continue. Please let me know.
>
>Brian,
>
>I've written myself a menu developer that I would love to make OOPy. If you like the ideas below, I can e-mail you a screen print and a sample of the generated code. If you are still interested, perhaps we can work together.
>
>1. Uses a treeview, lots of right-click options
>2. Generates the menu code
>3. Creates unique identifier for each pad, popup, and bar for security (see next point).
>4. Unlike the Foxpro menu developer, and all derivations thereof, allows you to cut and paste bars or entire branches, which *preserves*security*definitions*. This alone is really why I did it.
>5. Stores the menu definition in a table. This is cuz I want to extend the code generator to support the Active Toolbar and implement that Outlook-style stuff that's taking over Known Space.
>6. You never actually enter a command for the bars. You just specify which form to edit (all of my menu bars call forms). Since this is part of my pet roll-your-own RAD framework, it creates an instance of my standard form class if it can't find the named form.
>7. On the menu developer form, I have buttons, "EDIT FORM", "RENAME FORM", "NO FORM", etc.
>
>The result of this approach is that I have combined the job of defining a menu and working on the associated forms, I can do it all from one tool, which to my mind is the way the gods intended it.