Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Compiled EXE still looks for menu and procedure files th
Message
From
21/08/2002 17:27:02
Irv Adams
MSC Managed Care, Inc.
Florida, United States
 
 
To
21/08/2002 16:57:47
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00692181
Message ID:
00692242
Views:
20
Jim,

Try running Menu file w/o extension (if you're using one), just DO MENUNAME

HTH,

-Irv.


>The relative path info was in there, but when I took it out, then the app really didn't find the menu, even though it was in the VFP path. Do I need to include the MPR in the project as well as the MNX? I have not tried that before.
>>Jim,
>>
>>This is only a guess...
>>
>>In the code that runs the menu, or runs the .prg (or the set procedure command), is the path explicitely stated? For example, do you say something like:
>>
>>
do mrnu\menu1.mpr
>>
>>If so, remove the relative path from the DO command. In develop environment, you can use SET PATH to make sure it will find the procedures and menus when testing your app (when not running the .exe).
>>
>>>Hi all,
>>>
>>>I have had this problem forever, and I just made a quick-and-dirty fix to it for a long time. In order to get my compiled EXE to work on the target machine, I had to include under the home folder, a MRNU and a PROG folder with an instance of the menu file that it used and an instance of the procedure file (prg). When running, the app uses the latest version (compiled into it) and not the ancient ones in those folders. However, if they are not sitting there, it would not run.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform