>>>>>Maybe some DLLs are not installed on that machine?
>>>>>Maybe if you run Dependency Walker on that machine you will see what.
>>>>
>>>>
>>>>XFRX is in one folder on the server. It never needed any DLL installations. You dump it on server and it works.
>>>>Only dll used by xfrx AFAIK is zlib.dll
>>>>
>>>>What is confusing is why it crushes only on that machine not on any other ?? And only in case of using PNG.
>>>>If I switch bitmap back to bmp, it wld work.
>>>>
>>>>Type of bitmap (file on disc) is only thing that I changed, nothing else.
>>>>
>>>>Thank You anyway :)
>>>
>>>The only two DLLs XFRX used directly are ZLIB.DLL and HNDLIB.DLL.
>>>BUT the version of VS it is compiled may need more (like msvcrXX.DLL, msvcpXX.DLL etc).
>>
>>XFRX itself works. So I wld assume that these two dlls are ok.
>>Looks like this conversion from PNG is what is problematic.
>>
>>I will have to switch back to BMP for the time been (urgent), but I wld like to know how to fix this.
>
>Maybe the routine that handle the PNGs is messed up?

Huh I completey forgot to mention, this is an old report which uses PDFL library.
Method used is

.addPicture(tcFileName, tnXpos, tnYpos, tnWidth, tnHeight, tnAdjType) 

It might be very well backward compatibility by now...