Victorino,
What you are faced with is a direct FoxPro 2.x limitation, which is you can only have 5 "Reads" in effect at once. If you are using sepearte reads for each menu level, I recommend moving your menus to On top-line, type menu (using Fox menu-builder), and then creat Drop-down pads for your options. The menu builder has some nice things in it that allow you to control what is "Enabled" and "Disabled" in your menu, so that you can keep users from picking some item before they've selected some other item. (If that is the need you have). Another nice thing is, you can limit users from going into other "Screens" to do stuff before they've finished with the one they are in, if you get a lot of 'READs' going at once. (In a menu's Skip for Clause, you can put in something like: READLVL() > 4. Which says, as soon as you get 5 reads deep, disable the option.
This is no easy solution, and will require a bit of a re-think to your overall application structure, most likely. (Without being able to see your system, I don't know how you have it put together.)
The other thing is, use one base Menu (if you need to add on menu options as you go, that is also possible in Fox by adding "Additonal" menu pads, that you build, and enable based on a form being present.) Then create a single, "Foundation" Read, which keeps your menu present, and then you don't have to use another read for menuing.
This is more a theory answer than a direct solution to your problem, for which I appologize, but, it is going to take a re-think to get it to work how you want. (The good news is, it is possible!)
Best Regards,
Scott
Please let me know if this has helped
![[hammer] [hammer] [hammer]](/data/assets/smilies/hammer.gif)