|
Hi,
Thanks for the reply. I've got some more info on this issue.
First of all, to answer your questions :
We didn't make any changes to the test project (apart from the unlock codes), we've also tried with the image1.cmp, but with no luck. Only Leadtools 14.5 is installed, there are no other versions of Leadtools on those machines.
The version numbers are :
Windows 2000 (SP4)
Visual Basic 6 (SP5/SP6):
Visual SourceSafe 6a (8987)
Pdfdll32.dll : v. 8.53.0.0
ltr14n.dll : v.14.5.0.013
We've discovered that the problem appears when using Visual Studio and the Visual Source Safe Plugin (Add in in VB 6 (VB6.dll in System32)).
If we run just the executable of the demo app, everything works fine. When we run the VB6 project from within VB6, everything works if the Visual Source Safe add in is not loaded. When we run the VB6 project from within VB6 with the Visual Source Safe add in loaded into memory, blank pages are generated in the PDF.
It seems as if the source safe addin uses another system or shared DLL other than the one the PDF dll's use when running the executable. Are there any specific dll's other than the leadtools dll's (and the PDF folder + registry entry and pdfdll32.dll) the PDF compressor needs to run correctly ?
We already tried with service pack 5 and service pack 6 of VB6. We've also tried using the latest Leadtools patches. (downloaded about 2 weeks ago) and did a registry scan to check for corrupt entries.
We cannot deactivate the source control feature in VB6 to resolve this issue, since the rest of the application is also under source control and company policy prohibits otherwise.
Is there any way to get around this ?
Thanks for the help !
|