Re: ZLib Compression

You were right about the path issue. I followed your advice and copied zLib1.dll to the startup folder, and everything worked well.

Not sure what the version of zLib1.dll that was in the Programs Files\Inte\Wifi\bin directory was, but it was very recent and much larger than the zLib file I was using. Why I thought it was a 64 bit file is that all 32 bit applications are usually put into "Program Files (x86)" directory on 64 bit machines, not in the "Program Files" directory.

Anyway, it is working well now. Good to know that Web Connection can also handle this, but as everything is working I think I just leave it as it is. (Lazy!)

Steven

As the whole solution is working fine with zLib, I think

Web Connection 5.x comes with gzip support built in (actually using code based off John's code as well).

GZipping content from Response output:
wcdocs:_20d1empk9.htm

There are also routines the GzipCompressString() and GzipUncompressString() to work directly with strings for compression.

The wwHttp client also has support for decompressing GZip content from the server.

Your DLL load problem most likely is caused by a Path issue. If you want to be sure the right zlib.dll gets loaded put zlib.dll into your app's startup folder. Where are you seeing this error actually? Are you sure that's not coming from the Web server, rather than your application? zlib.dll is 32 bit only AFAIK.

+++ Rick ---

Hi,

I have an application that has been running on WebConnection for many years. In order to make transfer of data quicker, we are using ZLib to compress the data. As a wrapper to VFP I am using the it_Compression class published by John Burrows from InfoToday.

I recently changed to a 64 bit Windows 7 machine, and suddenly I have problems with ZLib. The error message I am getting is "Cannot load 32-bit DLL c:\Program Files\intel\wifi\bin\zlib1.dll"

Now, I am not sure that this is the place where the DLL should be. I never put it there, so maybe this is a 64 bit version of the program that came with the operating system. The file size is bigger in this version of the DLL than in previous versions.

Is there anyway I can tell FoxPro to look for this file in some other place?

Or maybe I am on the wrong track alltogether, and the problem is something else?

Steven