Creation password at runtime

[Cesar Davila Jr]

> -----Original Message-----
> From: filepro-list-bounces+cesar=stn.com at lists.celestial.com
> [mailto:filepro-list-bounces+cesar=stn.com at lists.celestial.com]On Behalf
> Of Kenneth Brody
> Sent: Friday, January 19, 2007 8:53 AM
> To: Bruce Easton
> Cc: filepro-list at lists.celestial.com
> Subject: RE: Creation password at runtime
>
>
> Quoting Bruce Easton (Thu, 18 Jan 2007 15:02:29 -0500):
> [...]
> > filePro 3.0 manual under "The Creation Password: Protecting Your
> > Formats,"
> > ...
> >
> > 	"This password does not, however, affect who can or
> > 	cannot see and change your records--runtime opertations
> > 	are protected separately with individual passwords."
> >
> > So if this definition has changed with the advent of variable-named
> > lookups, then why???  If the purpose of a creation password is no
> > longer just protecting formats and processing, then why is it still
> > called a creation password?
> [...]
>
> It's preventing you from creating a lookup into that file, just as a
> lookup with a hardcoded filename will require the creation password
> in *cabe.
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>

Hi Ken,

I've been working on this with Bruce and we understand what you are saying
and agree with it. So we did as suggested and placed the lookups in the
processing tables without the variable names so that we can be prompted for
the creation passwords when we tokenize.

What we are encountering is that the user is being prompted for the creation
password when they start using the application. The users are not "creating"
anything other than data. In fact, the application Bruce is working on is
simply trying to browse a series detail files.

Variable filenames are being used because of the potentially large number of
"qualified" keys.

In our tests, if we used normal lookups (without variable names), the
situation does not occur. Placing even just one of those lookups with a
variable name (and also including a dummy lookup with the real name so that
we do get prompted for the creation password) will trigger the effect of a
user having to type in the CREATION password when browsing the detail data
files.

Cesar Davila
Senior Systems Engineer

STN, Inc.
2127 Espey Ct. - Suite 100
Crofton, Maryland  21114
T: (410) 721-4004
F: (410) 721-9011
Email: cesar at stn.com