filePro/menus/scripts/etc (was Re: [SOLVED] EXPORT ASCII won't - after action report)

[Kenneth Brody]

On 6/10/2014 2:17 PM, Nancy Palmquist wrote:
[...]
> Example, I work on one app that the developer wrote with Batch DOS
> Scripts.  So instead of looking at the menu to see what happens, you
> have to hunt up a Script and then see what will happen.  It even goes to
> a filepro file and does IF THEN logic to decide which DOS script to run
> in some cases.  I find this approach very difficult to document and
> follow.  But it works.  I can see the beauty of a script to send an
> email or translate a PCL to a PDF where you can use it from anywhere,
> but filepro can run scripts right on the menus and it makes it easier to
> follow.  One less step of tracing.
[...]

I saw a system that had replaced all of the filePro menus with a filePro 
"menu" file, consisting of fields for the menu name, item keystroke, command 
to run, and comment.  (It looked as if all of the the filePro and user menus 
had been imported into this file.)  Then, there was a "permissions" table, 
which listed which users were allowed to run which choices on any given 
menu.  A master processing table was where everything started, which 
controlled access to all of the menus.

Elegant solution, but a pain initially to figure out what command line a 
particular user was running.

-- 
Kenneth Brody