Re: Menu Path solve
- From: "Dan Freeman" <spam@xxxxxxxxxxxxx>
- Date: Mon, 15 Aug 2005 09:25:47 -0700
Rule #1: NEVER MODIFY GENERATED CODE!
If you're building an exe (and you should be for distribution), the project
manager will resolve all pathing internally at compile time so this is a
non-issue.
Dan
dp wrote:
> Taking the "IN LOCFILE(.....) portion out of the menu generator allows
> menues truely to be integrated in APP/EXE files. With the standard
> menu generator you will have to include the menu.mpx in the original
> location which also does not allow to make a true setup where the
> enduser selects the destination directory.
>
> Scenario.
> app directory: F:\myproject
> source fiels: F:\myproject\source
>
> The menu on the developing machine with the other SCX and prg is in
> the source directory.
> Running the "standard" Menu generator will generate some code like
> ON SELECTION PAD _1hv06ai6t OF (m.cMenuName) ;
>
> DO _1hv06ai6u ;
>
> IN LOCFILE("\Myproject\sourc\MyMENU" ,"MPX;MPR|FXP;PRG" ,"WHERE is
> MyMENU?")
>
> Now if on the destination machine there is no directory
> Myproject\source then the above menu code will popup that file
> selection box asking for the MyMENU even though the menu had been
> included in the project and compiled into the app file and had been
> already executed with the "DO Mymenu.mpr ....." Command earlier in
> the code.
>
> Changing the code to
>
> ON SELECTION PAD _1hv06ai6t OF (m.cMenuName) ;
>
> DO _1hv06ai6u
>
> - ommitting the LOCFILE part will work and resolve the above problem.
.
- References:
- Menu Path solve
- From: dp
- Menu Path solve
- Prev by Date: Re: Protecting your code
- Next by Date: Re: Determine user's permissions on network server
- Previous by thread: Menu Path solve
- Next by thread: Protecting your code
- Index(es):
Relevant Pages
|
