filePro/menus/scripts/etc (was Re: [SOLVED] EXPORT ASCII won't - after action report)
Jay Ashworth
jra at baylink.com
Fri Jun 13 06:23:55 PDT 2014
----- Original Message -----
> From: "Kenneth Brody" <kenbrody at spamcop.net>
> 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.
Though it would make auditing easier.
Ah... the good old days.
My very first programming job was for Harris Data Corp, in 1981, on an IBM
System/23 Datamaster (the Model II's counterpart, though it had a fixed 3270-
like keyboard).
There was a batch language around BASIC, but you had no control flow.
So the work around was, Batch File A calls Basic Program A, which *asks questions
and then writes Batch File B*... which is the next thing Batch File A calls. I saw
(or did; I don't recall) this same thing later in CP/M on a North Star.
There was one spot in the system, IIRC, where that was like 7 or 8 levels deep.
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
More information about the Filepro-list
mailing list