>>Do you have the manual? If not, why not? The information you need is in chapter two, right at the beginning. I haven't worked with this product for a while, but I think that maybe if this information isn't in the help file, it may be planned that way in order to discourage pirated use of the product. Can't say I blame them. It's a very nice product, I'd try to protect it if it were mine. :)
>
>I don't see why it can be interpreted like that. All those OCXs are sent with a license file that only the developer has. A user does not have that file so he can't use the control in development. Or, maybe I misunderstool your question.
>
>As for me, I ordered it today by credit card. I didn't request the manual as they said the help is the same.
>
>I have sent them an email to know which files to distribute.
>
>Thanks.

michel,
since you don't have the book and i didn't see the info in the help file. this is what can be distributed ( according to the book ) for using the ocx interface.
dzip32.dll
dunzip32.dll
dzocx32.ocx
duzocx32.ocx
depending on how you are handling a progress monitor either of the below two may be needed
dzstat32.ocx
dzprog32.exe

and the standard ms ole support files ( they are listed in the help file under the registering 32 bit section )

just in case,
there is a special not that you may not distribute the license files or the help files but i'm sure you knew that.

hope that helps

one other thing, i think i've heard you say that you are using installshield.
i'm using 5.0 pro
and i had to register the components in a batch ( look for SELFRGISTERBATCH and SELFREGISTRATIONPROCESS in
the installshield help ).
what was happening to me is that it was trying to register the ocxs before it installed the dlls thus the registration process failed.