Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
XFRX and location of ZLIB
Message
 
 
À
21/07/2011 10:21:30
Information générale
Forum:
Visual FoxPro
Catégorie:
Produits tierce partie
Versions des environnements
Visual FoxPro:
VFP 9 SP2
Database:
MS SQL Server
Application:
Desktop
Divers
Thread ID:
01518769
Message ID:
01518772
Vues:
91
I have following code in XFRX wrapper to resolve similar problem
lcPath = "< Directory where  Zlib.dll is located >"
DECLARE long GetModuleHandle IN WIN32API string 
IF GetModuleHandle("Zlib.dll") = 0
	DECLARE long LoadLibrary IN WIN32API string 
	=LoadLibrary(ADDBS(lcPath) + "Zlib.dll")
ELSE
	*WAIT WINDOW "Zlib.dll already loaded"	
ENDIF	
>I ran into a weird issue yesterday and wonder if anyone else has wisdom on this.
>
>I cleaned up the folders for an existing app, getting rid of lots of stuff that's no longer in use, making sure all the files were in the right folders, and breaking up a very large classlib to create several smaller ones. Thanks the Class Browser and HackCX, plus some tools I wrote, this was a lot less painful than it could have been.
>
>Everyone's happy now, except one item. The app uses XFRX to create PDFs. In the development structure, we've put all FLLs and DLLs in a folder called LIBS. The FLLs are added to the project (and, of course, marked excluded). XFRX.PRG is in a PROGS folder.
>
>For testing at design time, we SET PATH to include those two folders (and a bunch of others), and everything works fine.
>
>At run time, the app's EXE is in a folder that includes all the FLLs and DLLs. Most things work fine, but when XRFX is asked to create a PDF, it complains that it "Cannot load ZLIB.DLL." We've found two workarounds, but we're not happy with either.
>
>Workaround 1 is to move ZLIB.DLL into the project's main folder, rather than the LIBS folder. Workaround two is to create a LIBS folder in the runtime environment and move ZLIB.DLL there.
>
>The XFRX docs say that things should work if the various libraries are in the same folder as the EXE that uses them or in the path. But we're finding that ZLIB doesn't seem to work that way. (Interestingly, no complaint about HNDLIB.DLL.)
>
>Anybody run across this? Better yet, anybody found a solution?
>
>Tamar
--sb--
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform