@ub and @cb issues - an idea

[Jay R. Ashworth]

On Wed, Apr 21, 2004 at 01:09:32PM -0400, GCC Consulting wrote:
> I wrote a physician's credentialing system which required much more
> tracking of who did what & when then even the *nix system maintained
> fields offered. It took a separate file(s) to track the information
> management wanted as to who did what & when. This included who
> looked or printed information(when by date & time) and 10 levels of
> modification tracking (complete "secret" copies of before(when "<U>
> was pressed & after snapshots of the data). Too much information to
> just track the change. It took 12 screens to get all of the data.

Ah, yes; auditing.

I've often wished for a *clean* way to get "what this field had in it
before I changed it" in WLF processing -- one, that is, that didn't
require either a WEF* with a temp dummy that couldn't have the proper
edit, or a separate routine for each field -- @PV would be nice.  :-)

> The above system had it's own login file controlling access to the
> system. One set of files was available to anyone. The other file
> had permission controls applied even before any data could be seen.
> This file required a second login to insure that someone other then
> the person logged in to the computer wasn't trying to access the
> restricted file.

I'm curious; assuming this was on Unix, why wasn't checking @ID good
enough for the security you needed?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson