Hi David,

I understand that I just don't see when to revert the levels. Having worked with rel. data for 15 years I find it hard to go back to the mainframe type of files with different record types. Headers and details all in one.
I thought someone has found a way to turn this mess into a simple structure like
_sysmenu file
file new
file open
.
.
.
file reports
reports rep 1
reports rep 2
..
_sysmenu edit

etc...


In other words a parent child relation


Peter


>Peter,
>
>The menu file is stored pretty linearly.
>
>Name gives you the individual item name, LevelName gives you the level at which an item appears. NumItems tells you how many sub items it has. ItemNum tells you which subitem it is. The Propmt without spaces becomes a Name/LevelName for tree branches.
>
>If you create a simple menu and look at the file it becomes wasy enough to see the structure.
>
>It's just a simple scan, skip the first row which contains the overall menu stuff. The order of the rows appears to be a depth order traversal of the menu tree.
>
>>Has anybody deciphered the menu file structure beyound the description wich comes with vfp
>>I want to create a tree type printout for documentation purposes. And the designes have never heard of relational design :-)