Hi Antonio,

>Great that you found it useful, Daniel.

This is really helpful and clean. I am feeling much more comfy with the Chilkat API:-)

I just inserted the stuff below:

** physically save the file resource before closing it
** unless the action is taken, it looks like the file is "in memory" (great)
IF m.ckZip.WriteAndClose() <> 1
MESSAGEBOX(m.ckZip.LastErrorText)
RETURN
ENDIF

Looks great since I am now just missing a few tricks:-)

One is related to type conversion. Since I have not practiced string conversion over the last fifteen years (oop!) and since our VFP app is a sheerly local tool, I tend to mix character translation requirements.

>m.ckZip.EncryptPassword = 0h000102030405060708090a0b0c0d0e0f1011121314151601718191a1b1c1d1e1f

I get it that this declaration as a fixed feed for binary information. The Chilkat site propose a much simpler: loZip.EncryptPassword = "myPassword". But it clearly does not work. I tried to replace the password entry with:
loZip.EncryptPassword = CAST("myPassword" AS W)

It then fully works but you cannot decode it in, say, peazip or winzip with the end-user password feed. I grasp it the password should possibly be converted to some extended multi-byte format. Am I correct? How could I transform the end-user single-byte ascii password string into an adequate entry in way that our users could get their hands on the zip file with their initial password?

>From Chilkat blog: Much fewer miscellaneous API additions were added in this release because most time and effort was devoted
>to the development of major new functionality (PDF).

Sure! Great to hear...

Daniel