FW: Processing Password Questions

[Nancy Palmquist]

Gary,

I know I am coming into the end of this thread, but I have to tell you 
that you should assign a site password in the beginning.  Write it down 
and put the password in the safe, make a copy of the fppath file it will 
create and put that in a safe place, you will never be stuck not knowing 
the password.  It will remain totally transparent until the system 
password does not match the process password.

SOAP BOX....  (As I have posted numerous times on this very subject...)

If you do not assign a password and it accidentally gets assigned later, 
as people always say, unbeknownst to them. (I love that word, not sure 
if I made it up or not but it fits.)

It will attach itself to each and every process table that you open and 
save, that has no password already.  This is transparent to the developer.

Then at some later time, the password is changed, removed or lost.  Now 
when you try to enter a process table, it prompts for a password and you 
do not know what it was.

VERY ANNOYING.

Now if you assign one and let it attach to all tables, if it ever asks 
you for a password, you know immediately that it was changed.  You can 
put the correct password back (from your carefully stored password 
notes.) and all will be well again.

When I helped fpTech with support, this was one of the common problems 
and I very strongly recommend that one always be assigned, even if it is 
"password" or "filepro" or something that simple.

SOAP BOX  -.... END

Saving in ASCII is great for two reasons in my book, it is faster and 
you can edit the tables without filePro - including the sitepassword 
data, if need be.

Nancy
-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com