Current menu script

[Jeff Harrison]

--- Kenneth Brody <kenbrody at bestweb.net> wrote:

[snip]

> 
> Okay.  I didn't realize that "modify all of the
> shell scripts to pass
> the information to filePro" was an option.  :-)
> 

Perhaps I was not clear.  I was modifying all of the
shell scripts anyway - by adding the following line as
the first thing in each script:

/appl/fp/dclerk lib -s1 -z logger -rw $0  

This is all fixed text that needs to be pre-pended to
each shell script.  Where the problem comes in now is
not in passing the menu script name, but passing the
"menu path" information.  

By this I mean that If the user presses 1 then A then
2 from the first presented menu (to go say 3 menus
deep), I would like to pass the string "1A2" into my
logger process.  I can't think of a way to that
without going into each script and adding a -r
"pathstring" though.  If you can tell me a paletable
way to do that I would be impressed :-)

I suppose I could load all of the menu items into a
filepro file, and then store the path information with
it - not paletable!  - I have written processes in the
past to import menus into filepro files, and I could
find them somewhere, but this is way to involved for
this application.

I guess I could figure out the path information based
on the log file itself if I also logged each user menu
selection that is itself another menu.  If I also add
the PID to the log file, then I can figure out the
various menu paths by printing a report that sorts by
user ID/PID/Date/Time.   Hmm...  I like!

Thanks Ken!  :-)

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHImport and JHExport. The fastest and
easiest ways to create code for filePro Imports and
Exports. 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com