Creation password at runtime

[Joe Chasan]

On Sat, Feb 03, 2007 at 02:53:01PM -0500, Jay R. Ashworth wrote:
> On Fri, Jan 19, 2007 at 10:02:14AM -0500, Cesar Davila Jr wrote:
> > 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.
> 
> I believe those two paragraphs are contradictory, alas.
> 
> A creation password is prompted for when a lookup to the file it
> protects is "bound" by filepro.  With fixed-named lookups, that binding
> happens at compile time.
> 
> With variable-named lookups, that binding does not happen until
> runtime.
> 
> I understand your problem, but I also understand their implementation,
> and I see why the other requirements of their implementation lead to
> this requirement.
> 
> And, honestly, I don't see any way they can satisfy those requirements
> and not cause this problem.

if the lookup exists elsewhere in the prc table in hardwired form, then
lookup to same filepro file or filepro file/qualifier combo using a 
variable can be excluded from such checks.  this satisfies both 
requirements but apparently would have to be a wishlist item for 
a future change/release as it is not coded that way right now.

--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
-Joe Chasan-                      Magnatech Business Systems, Inc.
joe at magnatechonline.com           Hicksville, NY - USA
http://www.MagnatechOnline.com    Tel.(516) 931-4444/Fax.(516) 931-1264