Creation password prompt at runtime

[John Esak]

>
> Which way does it fail a bad password?  Does it error out to a menu, or
> just fail the lookup?
>
> Cheers,
> -- jra
> --
> Jay R. Ashworth


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?
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.