Hi Mike,

>Absolutely nothing. If you persist passwords, someone can eventually figure it out. Don't think about writing your own encryption, either, because you'll get it wrong. Use the built-in Windows CryptoAPI to generate MD5 hashs of the passwords and persist those instead. There's a CryptoAPI sample in the VFP Solutions Samples.

Please, help me! :-) I have to save a password in a table because I need this password to "open" a encrypted file... If I do not save this password, the end-user must type it every day when open the application...

In this case, what should I do? ...

My solution was put this password encrypted inside a DBF. This DBF is encrypted by Cryptor and my EXE have this password... So, when my app is started, I "open" this dbf (encrypted by cryptor) and then read my password (that is encrypted too) ...

Are there some problems here?

TIA,