Thanks Dragan,

I'd definitely like to look at it.


>>I remember looking at a menu generation program (Venelina or Jordan if you read this was it from you all?) that would allow menu options and code to be executed to be put in a table and the menu could be generated on the fly in an app using the values in the table. Does anyone remember where it is from? We are looking at options for doing this soon. Eventually we would also like to be able to generate DBI's ctlistbar the same way if possible...
>
>I've had it back in FPD2.6. It's just that I never finished the transition of its editor into VFP - simply didn't need it. Frankly, the editor was just plain ugly, and the downside was also that I never added the recordtype field, so it was guessing like this "if the child key begins with a MN, it's a submenu, else it's a name of something to run".
>
>IOW, if you can provide a good way to populate the table, I have the runtime generator. It would have to be stripped off some extra code (like simulation of context-sensitive help based on currently selected bar, or some positioning thingies for the 25x80 screens) and you may well wish to keep some other stuff, like filtering based on security level or group. I really liked the filtering, because nobody saw any disabled bars in the popups - they simply weren't there, so they never got curious.
>
>And, BTW, I've mostly dropped this because I've converted the whole thing into a treeview, so instead of multiple levels of popups, I'd just have branches on the tree, and any form or whatever was invoked by clicking a node. Created at runtime from the same table, of course.