enter creation password when lookup with qualifiers?

[Bruce Easton]

GCC Consulting wroteWednesday, January 30, 2008 4:11 PM:
 
> > -----Original Message-----
> > From: filepro-list-
> > bounces+gccconsulting=comcast.net at lists.celestial.com [mailto:filepro-
> > list-bounces+gccconsulting=comcast.net at lists.celestial.com] On Behalf
> > Of Bruce Easton
> > Sent: Wednesday, January 30, 2008 4:03 PM
> > To: filepro list
> > Subject: RE: enter creation password when lookup with qualifiers?
> > 
> > joe at magnatechonline.com wrote Wednesday, January 30, 2008 2:36 PM:
> > 
> > [..]
> > >
> > > if you're talking about storing all this information in an additional
> > > file (aside from prc & tok), then may as well add another thing to
> > that
> > > file - which automatic table is to be associated with the particular
> > > prc table.
> > >
> > > --
> > > -Joe Chasan-                           Magnatech Business Systems,
> > Inc.
> > 
> > Important point that I was not clear on.  I was thinking the approved
> > list of files would be contained somehow in the tok table.  So my prior
> > statement that runtime programs would just be stripped of checking for
> > creation password could be done, but only if it were replaced with
> > the runtimes knowing from the toks (or some new external encoded file)
> > that certain file lookups had been pre-approved.  So, in essence,
> > from where we are now:
> > 
> > CREATION:
> > At attempt to save table - check lookups - prompt literally-named
> > lookups
> >   for any file with a creation password (CP)
> >   save table only if any prompted questions answered w/correct
> > password(s)
> > RUNTIME:
> > Prompt for any variably-named lookup file w/CP
> > -------------------------------------
> >       we could augment as follows:
> > -------------------------------------
> > CREATION:
> > Allow user w/hot key to enter one or more filenames to pre-authorize
> >   variably-named runtime lookups if evaluated to those files.
> >   (clerk prompts for the CPs for those files as they are requested.)
> >   (Only in memory at this point.)
> > At attempt to save table - check lookups - prompt literally-named
> >   lookups for any file with a creation password (CP).
> >   If successful - and file tokenized, then encode tok with files
> >   that were requested and pre-authorized in dialog above.
> > RUNTIME:
> > Prompt variably-named lookups for creation password IF it has not
> >   been pre-authorized and encoded in the tok.
> > 
> > Bruce
> > 
> > Bruce Easton
> > STN, Inc.
> > 
> The only piece necessary is that this be an encrypted file similar to
> processing tables so that it is not readable or editable using a text
> editor.
> 
> Richard Kreiss

Yes - that's what I meant by "encode tok", but if a new type of 
encrypted file holding the pre-authorized lookup files were used 
instead of the tok file (and the absence of such a file would 
indicate current behavior should apply), then this new 
functionality could be extended to work where quickstart is 
not used. 

Bruce

Bruce Easton
STN, Inc.