Creation password prompt at runtime
Jay R. Ashworth
jra at baylink.com
Tue Aug 3 08:15:00 PDT 2004
On Tue, Aug 03, 2004 at 01:20:00AM -0400, John Esak wrote:
> > Which way does it fail a bad password? Does it error out to a menu, or
> > just fail the lookup?
>
> Actually, if you leave the password thing to happen at Runtime, it is not
> very elegant at all... but how could it be? I never do this...
>
> However, if you were to do:
>
> @keyT if:
> then: ff="payrollfile"; ky=""
> if:
> then: lookup try=(ff) k=ky i=a -ng
> if:
> then: end
>
> You get.... the following if you don't know the password....
>
>
> *** A filePro Error Has Occurred ***
>
> On File: /u/appl/filepro/nexpremp/lockfile
>
> Input Processing
> Line Number: 5
> Incorrect password.?
>
> Like I said, not very elegant... but what else is there to do?
Just fail the lookup.
Optimally, they could leave a readable error code in some variable
somewhere, but there isn't one for that at the moment.
> I suggest not leaving passwords for runtime. I do lookups into our
> payroll file all the time so processes can test whether an employee
> is a manager or whatever. There is no need to show or use more of
> the sensitive file than required and putting the password in when you
> sae the processing is no big deal. It doesn't go anywhere... just
> let's you do this kind of thing... which is crucial.
That paragraph sounded like you both do, and do not, put runtime
passwords on files. Could you clarify?
Cheers,
-- jra
--
Jay R. Ashworth jra at baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274
"You know: I'm a fan of photosynthesis as much as the next guy,
but if God merely wanted us to smell the flowers, he wouldn't
have invented a 3GHz microprocessor and a 3D graphics board."
-- Luke Girardi
More information about the Filepro-list
mailing list