Creation password at runtime

[Bruce Easton]

Thanks for the repsonses on this.  Although I do see why you might want a
runtime password to protect access to data, I do not see the reason for a
creation password being asked of an end-user - ever.  And in many client
situations, I would never want any of the client end-users to know what any
of the creation passwords are.  If I may quote page 9-23 from the old
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?

I backed up, then removed all of the qualified keys/datas/indexes/lockfiles
except for four of them (leaving me with [none],MD1,MD10,MD11 and MD12). At
the top of the called table that I quoted from below, I added five lookups:

lookup APP  k=td i=A -ng
lookup APP at MD1  k=td  i=A -ng
lookup APP at MD10  k=td  i=A -ng
lookup APP at MD11  k=td  i=A -ng
lookup APP at MD12  k=td  i=A -ng

The program still asks me for the CREATION password when I tokenize the
table (for file 'APP') and then asks for it again at RUNTIME. Still makin'
no sense to me.

Bruce
-------------------------------

Ken Brody wrote on January 17, 2007 7:29 PM:

> This is the way filePro has always handled variable lookups.  Consider
> the following code snippet to understand why:
>
>    fn = "payroll"
>    id = "the boss"
>    lookup foo = (fn) k=id i=a -nx
>

and,

John Esak wrote on January 17, 2007 7:05 PM:
>
>
> A pain, but just do an extra lookup somewhere on the table that uses the
> real filename and not a variable. This way you'll be asked for
> the password
> at when storing the table and not at runtime.
>
> John Esak
>
>
> > -----Original Message-----
> > From: filepro-list-bounces+john=valar.com at lists.celestial.com
> > [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com]On
> > Behalf Of Bruce Easton
> > Sent: Wednesday, January 17, 2007 6:07 PM
> > To: filepro-list at lists.celestial.com
> > Subject: Creation password at runtime
> >
> >
> > I am getting prompted for a Creation Password at runtime during the
> > execution of a called table.  Just doesn't seem fair.   My code uses a
> > variable name for lookup (for read purposes only) into a
> qualified key of
> > the file that seems to be in question here:
> >
> >         If: 'portion of called table
> >       Then: ii(2,.0)="1"
> > iiloop  If: ii gt "30"
> >       Then: xu=xu+"1"; goto xuloop  'somewhere above all this
> >         If:
> >       Then: xf="APP at MD"{ii
> >         If:
> >       Then: lookup  thefile = (xf)  k=td  i=A  -ng
> >         If: not thefile
> >       Then: xu=xu+"1"; goto xuloop
> >         If:
> >       Then: 'other stuff gets done here
> >         If:
> >       Then: ii=ii+"1"; goto iiloop
> >
> > The program does work OK without error, and will return the
> > desired results
> > if at runtime, I enter the Creation password for the file "APP"
> - the same
> > password that is required when I use rcabe for anything that
> looks up into
> > that file.  File "APP" has 30+  qualified keys (and for the
> love of warmer
> > weather, I have no idea why someone would design it that way, but
> > hey).  SCO
> > Unix - filePro is 5.0.14.
> >
> >
> > Bruce Easton
> > STN, Inc.
> >