cancel
Showing results for 
Search instead for 
Did you mean: 

Dynamic Image Scaling Problem with Crystal Reports XI Runtimes

Former Member
0 Kudos

I am using the Crystal Reports XI dyanmic image feature to place a photograph on a report based on an image path stored in the database. The image is correctly retrieved and displayed, but the resulting output is an incorrectly scaled photo. Instead of stretching / shrinking the image to fit the size of the existing object on the report, the image ends up being extremely small and jammed into the upper left hand corner of the object position.

The report is being deployed as part of our software application.

When I preview the report in Crystal XI Developer, the output looks fine. When I run the report through our application on a server with the Crystal XI Runtimes installed, I get the above behaviour. However, if I run the report through our application using a server that has the full version of Crystal XI installed, then the image output looks fine.

Does anyone know if there is an issue with the Runtimes / Merge Modules relating to dynamic images? If so, does anyone know which dll needs to be updated? If not, has anyone seen anything like this before?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Some important details are missing-

CR Version?

VS Version?

Windows or web application?

What runtimes you have installed?

To install latest runtimes click [here|http://resources.businessobjects.com/support/additional_downloads/runtime.asp]

Note - Click the link according to the CR version and the service pack installed on your development machine.

The Wiki is [here|https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsforVisualStudio.NETRuntimeDistribution-Versions9.1to12.0]

is currently the best resource for CR.NET Runtime information.

Hope this will help!!

Regards,

Amit

Former Member
0 Kudos

Hi Amit,

I am using the RDC packages. I rebuilt the runtimes installer using the SP4 merge modules currently available. After I deployed the new runtimes to the server, the problem has gone away. I suspect this is something that was resolved in one of the service packs. Thanks for you help.

Jeff

Answers (0)