>Hi Jim,
>
>>The menu setup code won't work for you, it only runs once when you DO
>>Menu.mpr and never runs again. There is no way to get the parameter you
>>want into the menu to be passed on to the called form, so you'll need to
>>develop a another way to get that parameter into the form.
>
>In FP 2.x you could define a variable in a PRG at the module level and it
>would be available to any PROCs in that PRG. I was under the impression
>that, since the Menu Designer was a holdover from the 2.x way of doing
>things rather than an OOP tool, it would still work the same. Even though
>the menu's setup code would only be executed once, why wouldn't the PROCs
>in the MPR have availability to any variables defined in setup?
>
>Thanks for the example. You've given me quite a lot to look over today.
>
>
>Gary J. Sibio
Gary,

The reason the vars won't be available is that the MPR runs, defines the menu, and then ends and returns control to the calling program. When the MPR returns its vars go out of scope as do the procedures defined in the MPR.