Turning on encryption in filePro 5.7.03

[Mike Schwartz]

> 1. Each file needs to be encrypted separately 2. The encryption is
invisible
> to the user 3. If you are doing programming either in a development or on
> your own system, you will have to have the same encryption code on your
> system otherwise you won't be able to read the file.
> 4. The file encryption and field encryption are different.  The file
encryption
> will make the file unreadable from outside filePro.  Field encryption
> encrypts the field and it is unreadable within filepro unless decrypted.
> Fields with Social security numbers or other private information are
usually
> encrypted at the field level to prevent prying eyes from seeing these
fields.
> 5. It takes a bit of time to learn how to use field encryption properly.
> You need to make sure that what you encrypt can be decrypted properly.
> 
> I understand that FPtech is working on a way to encrypt all files at once
but
> for now you need to do this one at a time.  Also keep in mind that for
now,
> indexes are not encrypted.
> 
> Richard Kreiss

     Thanks for the all the info.  For now, they just want the whole files
encrypted, in case somebody breaks into their server and is able to search
for and see the raw data files.   

     The multiple-file encryption would be nice.  They have a couple of
hundred files. but I've suggested that they probably don't need to encrypt
files that don't have any confidential user data in them,  like STATES.
They are making a list of the filePro files that have any confidential data
right now.

     And, yes, I'm definitely going to make multiple backups and test the
encryption thoroughly before I release the files to them...

Mike Schwartz