>>>>>Ed, This approach works great. Thanks for the tip. I have another question, if you don't mind. One of the menu pads is devoted to printing reports. For each report, I give the user the option to print to printer or screen. When I run the compiled exe on our network, the menu works fine except for this:
>>>>>
>>>>>After the user prints a report to the screen, all of the menu pads are enabled (as they should be), and when I select a menu pad, the corresponding sub-menu appears. The problem is that nothing happens when I select one of the sub-menu pads. This does not happen when I run the app on my C: drive. Any ideas?
>>>>>
>>>>>Thanks, AL
>>>>
>>>>What code is under this pad? And it will be better if you put details here as beginning of new thread. It will be helpful for you, first of all, because many UT experts will get opportunity to contribute efficiently.
>>>
>>>REPORT FORM culisting.frx TO PRINTER NOCONSOLE PREVIEW
>>
>>Some minor points:
>>1.Use Report Form culisting ... (w/out frx) if you include report file into executable.
>>2.Add some WAIT Window "Ok" as first procedure line for test, to make sure that you really fire the snippet.
>>3. Do you use Report.DE ? If not, then you have to Select work area before issuing Report Form command.
>
>The problem is not that the report doesn't print to preview - it does. The problem is AFTER I CLOSE the preview window the menu items are enabled (which they should be) but NOTHING happens when I select an item from one of the sub-menus (eg. if the sub-menu pad command is to open a form - nothing happens). Once again, this only happens when I run the exe from thge network - not when I run the 'uncompiled' app on my c: drive.
>
>By the way, I do use report.DE

Do you mean that you cannot invoke any command from any menu snippet? Even messagebox()?