Password Problem Revisited

Richard D. Williams richard at appgrp.net
Fri Jun 11 13:22:26 PDT 2004


Vicky,

I have seen this strange thing as well. Sometimes when I am coding my 
fingers must hit some combination of keys and a filepro window pops up 
asking if I want to set a processing table password.

Since I am working on the processing table I already know there is NO 
password set.  I have simply pressed enter and went on about my business 
of coding.  Still wandering....... what keys did I press to get this 
little window up?

That maybe your problem.  But this is not a solution.

FP tech can take these pesky passowrd off for you (for a fee.)  Contact 
them.

Sorry I can help you,
Richard D. Wiliams

Jean-Pierre A. Radley wrote:

>Vicky Prigg propounded (on Fri, Jun 11, 2004 at 12:38:12PM -0400):
>| 
>| Despite some good suggestions, we have not solved our password problem.
>| It is not a site password as some have suggested, rather it is a
>| 'processing password' that has somehow been acquired by some (not all)
>| of our processing tables.  It was not a one time thing that happened to
>| all the processing tables present at the time.  It happened to a few,
>| while not affecting others.  And, it is not a case where someone gave a
>| password to a processing table and forgot it.   We cannot use backup
>| tapes because they have long since been recycled.  We do have an fppath
>| file in the directory /etc/default and it is set to /appl .  Is there a
>| way to convert processing that was not saved as ASCII to an ASCII
>| format?  Some of the processing tables were saved as ASCII and those I
>| can use vi to remove the password.  Others were not saved as ASCII.  We
>| have since set ABE = ascii so any future programs should not be a
>| problem.  I know that fptech can do this for us, but we have quite a
>| number of programs that would require fixing and it would be quite
>| costly.  Also, if anyone has any ideas as to how this happened in the
>| first place, please let me know!  
>
>If you have ABE=ASCII in your config file, then run dcabe, open such a
>non-ascii table, save it, and presto, it's once again legible.
>
>  
>



More information about the Filepro-list mailing list