Or just use this as your FILELIST profile: /* */ 'MACRO PROFFLST' 'set pf2 before macro execute cursor BROWSE'
(The below was QAD and didn't need the B EXEC.) Brian Nielsen On Thu, 13 Dec 2007 16:37:29 -0600, Brian Nielsen <[EMAIL PROTECTED] > wrote: >Create the 2 files shown below, then use FL instead of FILEIST. Feel free >to change the names to suit your taste. > >FL EXEC >------------------- >/* */ >arg data >push 'set pf2 before macro execute cursor exec b' >'FILELIST' data > >B EXEC >--------------- >/* */ >arg data >'browse' data > > >Brian Nielsen > >On Thu, 13 Dec 2007 16:19:02 -0600, Ron Schmiedge ><[EMAIL PROTECTED]> wrote: > >>Nope, never :-) >> >>What I like about FLIST is I can easily set up the PF keys the way I >>want (see FLIST $PROFILE). We have used this to give users customized >>things they can do. Including removing the ability to edit the files >>(ever have a user edit a listing to change the numbers on a report, >>rather than correct the input data and rerun the program?). >> >>I like the REFRESH PF key in FILELIST, but having been an FLIST user >>since about 1979, its a hard thing to switch to. Since PF2 is BROWSE >>in FLIST, I waste a lot of time in FILELIST refreshing the screen.... >> >>Ron >> >>On 12/13/07, Kris Buelens <[EMAIL PROTECTED]> wrote: >>> The great advantage of FILELIST is that you have the full power of >>> XEDIT to manage the list. I switched from FULIST to FILELIST with >>> FILELIST's second release of (VM/SP Rel 2?) when one no longer had to >>> press PF10 to get the commands executed.... >>> >>> Do users of FLIST never miss something like >>> ALL /this/ & /that/ >>> followed by for example >>> EXECUTE * COPY / = = X (OLDD >>> >>======================== ========================= ========================
