Roxanne,

I went with data-driven menus because I could not cut and paste with Fox's menu generator.

I took the project as an excuse to get up to speed with TreeViews and Drag'n'Drop, and wrote myself a menu generator that displays the menu in a treeview, and allows you to cut branches out of it and paste them elsewhere. Since *all* of my menu bars call forms, I put a little textbox to enter the form, and then threw in some code to create a form out of my default class if the form did not exist when first entered. Then of course it seemed like a good idea to put on some buttons to edit the form, delete the form, and there went the weekend :).

Pros: My Menu pads and bars are well-defined objects that can be assigned security priveleges. I or my minions can make a mistake and just cut-n-paste an entire branch without having to rekey the whole thing and lose the security definitions.

Cons: No compatibility with the MNX format, had to write it myself.

Pro/Con: Depending on how you like things, my own generator builds a static PRG that builds the menu, the menu is not built at run-time. However, re-working the code to build the menu on-the-fly is not too tough, that's how I always did it in the pre-VFP days.

The whole thing is wrapped up in my framework's project development form. If you'd like to take a look, it probably would not take long to cut the strings and make the thing free-standing.

>Where have I heard this before?? Seems to me, like a year ago, I heard/seen/caught wind of some neat trick for building menus and/or shortcut menus off of meta data in a table.
>
>I'm on a mission & searching now, but I was wondering if this rang any bells for anyone? TIA!