>Edward, We tried the same with the option, but for the TEXT
>pad. all the other options could be disabled using the above
>command, but whatever command you give the text pad appears in
>the user created menu.
>
>We checked some sample programs/menus spplied along with the
>software. on observing the menu codes developed, we noticed
>that all the menu's developed were not directly called from
>a screen set. Well, at last we gave it a try, by calling/
>executing our menu program from a sample screen developed, and
>it worked the way it wanted to be. Are we conclude that a menu
>code when called independantly would add the text pad???
>since creating a dummy screen and then calling the menu program
>is clearly acace of more consumption of memory.
>
>Ahmad

I meant that _MTEXT pad if added to menu design will allow to use SKIP clause. Sometimes I saw on my screen that changing of a variable for this clause doesn't 'refresh' the menu, i.e. pad looks enabled but in fact if clicked is disabled. It wotks better for bars because they are always refreshed when pad is clicked.