enter creation password when lookup with qualifiers?

Kenneth Brody kenbrody at bestweb.net
Tue Jan 29 16:27:56 PST 2008


Quoting GCC Consulting (Tue, 29 Jan 2008 17:19:40 -0500):
>> -----Original Message-----
>> From: Kenneth Brody [mailto:kenbrody at bestweb.net]
>> Quoting GCC Consulting (Tue, 29 Jan 2008 12:34:14 -0500):
>>
>> [... Why does filePro ask for a creation password at runtime on a ...]
>> {... variable lookup? ...]
>>
>> >> > ky = "myself"
>> >> > fn = "employees"
>> >> > lookup salary = (fn) k=ky i=a -nxp
>> >> > salary[10] = salary[10] * "1.5"
>> >> > write salary
>>
>> [...]
>>
>> > If fp didn't want to break the current code regarding the creation
>> > password and lookups using a variable, there are 2 solutions:
>> >
>> > 	1. Another environmental variable pfcrpw=no  Turn off asking for
>> >    the creation password at runtime
>> > 	2. Ability to bypass the password at runtime in programming with
>> >    a lookup flag to bypass the creation password request.
>> >
>> > This last option does can offer some runtime security by allowing
>> > using a variable but based on the user allow access directly or
>> > require a password.
>>
>> And these solutions differ from "don't ask for the password", how?
>
> It gives the developer the opportunity to decide when the password would be
> used in *cabe and still have the use of the creation password.
>
> My preference is for option 2.  This allows for more finite control as one
> could have to lookup line which execute one with a password one without
> depending on specific criteria such as who the user is.

And what stops John Q. Employee from writing the above code, plus the
flag to lookup?

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com


More information about the Filepro-list mailing list