Creation password

[Bruce Easton]

I guess if you had a limited number of files involved (being looked up), 
then what John recommended might be helpful if you're trying to avoid 
multiple processing tables doing the same thing.  I haven't tried that, 
so I don't know if it works.

I first ran into this years ago when writing some utility software that, 
by design, would not know until runtime which filepro files a customer 
might have that would be looked up from it. That's when I first 
discovered that filepro asks for the CP at runtime for lookups formed 
with variable names.  So I believe such behavior probably started with 
the advent of the variable-named lookup capability.

There was some discussion on the list answering:

a) why such behavior was necessary (backward compatibility of original 
security intent of the CP) and
b) why, in hindsight, it perhaps could have been implemented differently 
(so that anyone wanting to write software against unknown filepro 
filenames could do so and sell runtimes of such software and not have 
end-users being asked for CPs at runtime); or that perhaps an alternate 
behavior could be offered.


On 5/30/17 6:24 PM, Richard Kreiss wrote:
> Yes,
>
> And I saw that John Esak had recommended doing a lookup using the full name
> first.
>
> There are too many programs that would have to have this code implemented to
> so this now.
>
> Hate it when the original documents say one thing, and later releases change
> how this option behaves but is not documented anywhere.
>
> Also, the readme file for the installation has not been update since version
> 5.0.15.  I think that was 2006.
>
> Richard
>
>
>> -----Original Message-----
>> From: Filepro-list [mailto:filepro-list-
>> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Bruce Easton
> via
>> Filepro-list
>> Sent: Tuesday, May 30, 2017 4:47 PM
>> To: filepro-list at lists.celestial.com
>> Subject: Re: Creation password
>>
>> Is the file that has the creation password being looked up in your
> processing via
>> variable name/expression?
>>
>> On 5/30/17 4:43 PM, Richard Kreiss via Filepro-list wrote:
>>> Doesn't answer the main question.
>>>
>>> The simple answer is to remove the creation password.
>>>
>>> I have checked back manuals and found the following:
>>> Profile 16 -
>>> 1. ..."you can define a "creation" password when you define a your file.
>>> The program the asks for this password as the start of each formatting
>>> program.
>>> 2. You can define "format" passwords.  These passwords limit access to
>>> the data contained on particular screens.
>>>
>>> Stuart Warner's Filepro Plus Developer's Reference 4th Edition
>>> Creation Password (generally, avoid using passwords).
>>> The creation password protects access to of the creation programs for
>>> this file.
>>>
>>> I am not sure where a change in behavior may have occurred.  But my
>>> understanding is that a creation password should not have an effect on
>>> *clerk or *report.
>>>
>>> The only time, per the filePro manual that a file with a passworded
> screen.
>>> Then any field on that screen would need a password entered on an
> output.
>>> Richard Kreiss
>>>
>>>
>>>> -----Original Message-----
>>>> From: Filepro-list [mailto:filepro-list-
>>>> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Walter
>>> Vaughan
>>>> Jr via Filepro-list
>>>> Sent: Tuesday, May 30, 2017 9:45 AM
>>>> To: filepro-list at lists.celestial.com
>>>> Subject: RE: Creation password
>>>>
>>>> What happened when you  googled the archives of this list?
>>>> https://www.google.com/?gws_rd=ssl#q=site:mailman.celestial.com/piper
>>>> mail/
>>>> filepro-list/+creation
>>>>
>>>> -----Original Message-----
>>>> From: Filepro-list [mailto:filepro-list-
>>>> bounces+wvaughan=steelerubber.com at lists.celestial.com] On Behalf Of
>>>> Richard Kreiss via Filepro-list
>>>> Sent: Monday, May 29, 2017 12:21 AM
>>>> To: Filepro 2 List <filepro-list at lists.celestial.com>
>>>> Subject: Creation password
>>>>
>>>> If a creation password is added to a file. At runtime is filePro
>>>> supposed
>>> to as for
>>>> that password?
>>>>
>>>> If yes, is there a way to by-pass this as it creates havoc with tasks
>>>> that
>>> run at
>>>> night and slows tasks during the day.
>>>>
>>>> Richard Kreiss
>>>> Sent from my iPhone
>>>> _______________________________________________
>>>> Filepro-list mailing list
>>>> Filepro-list at lists.celestial.com
>>>> Subscribe/Unsubscribe/Subscription Changes
>>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>> _______________________________________________
>>>> Filepro-list mailing list
>>>> Filepro-list at lists.celestial.com
>>>> Subscribe/Unsubscribe/Subscription Changes
>>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> Subscribe/Unsubscribe/Subscription Changes
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus