>Hi all of you,
>
>Per default, our VFP applications save most of its information in plain text format. Easy read and easy write in fox!
>
>We are contemplating offering an optional "AES-encryption-zip" file format as an alternative and I was giving a look at the "Chilkat suite" activeX in this respect.
>
>My question(s) is(are) pretty simple :
>- can Chilkat easily transform a VFP string into an AES zipped file resource?
>- can you unzip this zip file straight back into an un-encrypted VFP string?
>
>I expect the answers to be yes. But I am concerned about the process to be fully and safely "in-memory". Should we decide to offer encryption, we certainly NOT to hear that the process requires building un-encrypted temp files as intermediate steps!
>
>Kind regard for any feedback on this issue and, at large, Chilkat suite usability from VFP. Looks like some sort of win32 "swiss knife" for the VFP die-hard such as those on this forum!
>
>Cheers, Daniel

I've been using Chilkat for over 10 years. It has saved my bacon more than once.

We use it regularly for encryption, http requests with querystring or post data, email, FTP. ZIP, custom XML work, etc.

We use it in our Lianja products: same code as we've already written for our libraries in VFP.

Plus, the Chilkat Controls are regularly updated with the latest versions of encryption, compression, etc., once they become stable.

And the examples are fantastic. Getting my head around diffie-hellman, and doing it the right way, would take this slow learner a lot of time. Using the example(s) given and the riffing as needed makes that part of the task a breeze.

Hank