FW: Processing Password Questions

[Nancy Palmquist]

Guys,

I see that many people are suggesting that the passwords are an 
annoyance but I still disagree.

They are invisible to me on my development system.  When I install 
programming on the customer computer, if they own a development system, 
they are unable to access the tables without the password.  I am able to 
see the tables if I need to do so.

I can also assign a special password for just one customer's files. 
PFSP=password

I like this if the customer might want to buy source code later.  All 
you have to do is give them the correct site password that was attached 
during development.  Easy to do and it will allow you to assign a 
different one to different projects.  It also allows me to work on a 
client's development without attaching an incorrect password.  This 
assumes you do not use ABE=ASCII to store the tables.  If you do, a 
little editor can remove the password in a blink.

Now this all assumes that you commonly work with untokenized tables, 
which I do on some systems that pre-date the inclusion of Quickstart 
with basic filePro.  If you distribute only tok. tables, site password 
are useless entirely.

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.

Well, of course, they can be removed.  They are never seen at runtime, 
unless you try to access the debugger.

I just think it is an easy way to avoid "big problems" later on.

Now that all opinions have been voiced, you can decide what will be best 
for you.

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