FW: Processing Password Questions

[Jeff Harrison]

--- Fairlight <fairlite at fairlite.com> wrote:

> On Wed, Dec 28, 2005 at 02:25:20PM -0500, Nancy
> Palmquist may or may not have
> proven themselves an utter git by pronouncing:
> > 
> > But the problem comes when you have none, and it
> is accidentally 
> > assigned along the way.  As a developer, you will
> not notice any 
> > difference, but each process that is saved will be
> polluted with the 
> > password.
> > 
> > If you set one and let it attach to every table
> you update, it will 
> > never attach a password you do not know.
> 
> And how might this happen?  filePro just doesn't
> randomly tack in passwords
> when they haven't been assigned at all at any point
> in time.  This means a
> password was entered -at some point-.  This stuff
> doesn't "just appear" out
> of nowhere, sorry.
> 
> Possible explanations:
> 

[snip]
I agree that random doesn't usually happen :-) 
However, things in the computing world often appear to
be random.  For example the case in point that started
this thread.

While It has never happened to me, I can see that it
would be easy - especially for someone not overly
familiar with the PFPATH file - for someone to enter a
fourth line without realizing exactly what they are
doing - perhaps they are trying to get filepro to look
in two possible places for its data.  Or perhaps they
just enter some text there as a comment.  

I agree, though.  For ME site passwords are usually
not worth the trouble.  I do use them though as a way
to give a little bit of protection to my JHExport and
JHimport demos.   

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and imports.


	
		
__________________________________ 
Yahoo! for Good - Make a difference this year. 
http://brand.yahoo.com/cybergivingweek2005/