The former's correct for ZipString() method only. In all other cases the vfpCompression.fll creates a complete ZIP file that is recognizable by other zip-type applications.


>I agree with using the vfpCompression.fll. But from experience I had a few problems. First, the resulting compressed string cannot be written out to a file directly. It does not have the needed header to allow zip-type application to recognize it. It can only be managed with the utility itself. Second, when we used it excessively, we started to experience C5 errors. There appeared to be a memory leak occurring. Now, with hope, these issues have been addressed in the last few years, and the current version is more stable. Sorry, just speaking from experience.