Crystal Reports Dynamic Image Includer cViewIMAGE, Developer License

Crystal Reports Dynamic Image Includer cViewIMAGE, Developer License
A Note About Licensing:
The developer license allows you to dynamically include images in your reports. For people to be able to see those images, each client needs a cViewIMAGE seat as well (two free seats come with cViewIMAGE). On the next page, you'll pick your license quantity based on the number of users.

Crystal Reports Dynamic Image Includer cViewIMAGE, Developer License

Price: $149.95

Quantity in Cart: None


Dynamic Image: display images from a folder, not a database. cViewIMAGE calculates the file + path name from fields in your database without storing images in your database. Make your reports sharper and more powerful. Free 30-day trial.

Give your Crystal Reports the ability to send crystal clear messages, by dynamically including images.

If you wish to include cViewIMAGE in your application and distribute it to your customers, please see our cViewIMAGE Pro license.

How it works

cViewIMAGE allows a developer to design a report that calls images for dynamic inclusion in those reports. To see those images, the clients must also have cViewIMAGE installed. cViewIMAGE enables you to include images in your Crystal report even if they are not stored in a database. Hold the reference to the image e.g. c:\Product Images in your database, instead of the image, and cViewIMAGE will retrieve them from the folder for your Crystal report.

  • cViewIMAGE uses a COM data driver to create a recordset you can use in your Crystal Report to include a dynamic image in your report.

  • cViewIMAGE includes a SingleIMAGE driver that takes an image file name and presents it in a recordset to use in your report. This will work well inside a subreport. There is also an ImageFolder driver that will return all the pictures from a folder.
  • cViewIMAGE requires Crystal Reports 8.5 or higher to process the recordset. Yes, it works with CR8.5, 9.0, 10.0, and XI.

You do not need the image to be stored in your database. Your database simply holds the file path to the image, not the image itself.

The advantages are that:

  • Your database is very much smaller than if it were storing images.
  • It's easier to manage your images. Adding, changing and deleting images is simpler if they are stored in a folder rather than held in a database.

    How would you use cViewIMAGE to do it? To put your image of say, your product into your Crystal report, you would create a new connection using cViewIMAGE as well as your normal Product database/file connection. Then write a formula to access the file path reference of the image (e.g. c:\Product Images) from your Product database to point cViewIMAGE to the folder/s where your images are filed. Then place the image in your report along with any other information from your Product database.

  • Why cViewIMAGE

    Why dynamically include an image in a report? Images are compelling and give a report great eye appeal. You can use them to convey information in ways that text alone cannot. You probably already guessed we would say it: A picture's worth 1,000 words.

    Why use cViewIMAGE to do it? cViewIMAGE offers functionality not available by other means (see the cViewIMAGE v. Crystal XI tab).

    cViewIMAGE is one of our best-selling products. Once you start using it, you'll understand why.


    Each client machine needs a cViewIMAGE client license (seat) to view the images the developer dynamically includes in the report. You get two free seats with it. Buy additional seats, as needed.

    vs. Crystal XI

    While XI does support dynamic images using its own mechanism, it still supports cViewIMAGE. The ImageFolder driver in cViewIMAGE brings in all the pictures from a folder--something XI can't do. cViewIMAGE does have functionality which is still not available in Crystal in this form and as far as we are aware, is not planned to be in later versions of Crystal.

    So there are still benefits in using cViewIMAGE even if you have Crystal XI or Crystal 2008, depending on what you are trying to do.

    By using different arguments, you can pick up different cViewIMAGE COM drivers which provide different functionality.

    Functionality available only in cViewIMAGE as far as we are aware:

    • cViewIMAGE.ImageFolder enabling you to import an entire folder of images, providing multiple images which can be based on a wild card.
    • cViewIMAGE.ImageSize enabling you to specify height and width of your image (from cViewIMAGE version 4)
    • cViewIMAGE.ODBCImage enabling you to include a set of fields as well as the embedded image (from cViewIMAGE version 5)

    The functionality now available in Crystal XI that is similar to other cViewIMAGE COM drivers: cViewIMAGE.WebImage (from cViewIMAGE version 4) and cViewIMAGE.SingleImage (often used)


    cViewIMAGE gives you a great deal of flexibility, regarding where you store your images and what sizes they happen to be:

    Different image sizes Images stored in different locations

    There are issues with different sizes of images and how good different resolutions appear in print. To address many of the issues, we have a driver that enables you to specify the height and width of the image.

    To use the driver, select cViewIMAGE.ImageSize instead of the more usual cViewIMAGE.SingleImage.

    The major hurdle to overcome is that Crystal Reports has a Fixed/Total image size option when you put an image field on the report. There is no way to dynamically change the size of any object on the page (apart from “Can Grow”).

    While you may have many images, you will probably find that there are several basic shapes that most will apply to.

    cViewIMAGE can cope with your images being in different locations as long as you can write a formula to include the conditions on how to find them. There is just one formula to be written to enable cViewIMAGE dynamically link the image reference in the database to the actual location of where the image is stored.

    For example, you may have architectural drawings in your c:\Architect folder and your building photographs in d:\Photos.

    Or you may have all your drawings named Arch001 etc and your photos named Photos001 etc. If the images are named or located in a way you can describe in a formula, cViewIMAGE can find them and display them in the report using that formula.

    Image location on a file share isn’t really a problem but everything works a lot faster if they are on a local drive.

    “Can Grow” can create very large images on a page. But a better solution is to use conditional sections to control the way to get different shaped pictures on the page.

    Create multiple sections in your report with various shapes and the use conditional section suppress to select which section will appear with the correct aspect ratio.The way to do this is have several copies of the same image field from cViewIMAGE record, each with a different height/width ratio. Then you select which image you want based on the size fields in the cViewIMAGE record. The cViewIMAGE.ImageSize fields includes those as extra fields along with the embedded Image.

    A formula which calculates the aspect ratio of the image (height/width) is useful here.A value of 1 suggests a square picture, a value of 2 would indicate a portrait orientation and a value of 0.5 would be a landscape image.So this is not totally dynamic sizing, but in reality close enough as most images are in a finite set of sizes. Portrait, Landscape and Square would cover 75 – 90% of most image collections. You can add a few more special sizes if you need them.


    cViewIMAGE supports only the Crystal-supported formats. For example, it supports jpg, bmp, and WMF but not GIFF.

    Although Portable Document Format (PDF) is popular, it’s not an image format. It is exactly what the name says: a way to preserve formatting of a document for portability.


    Here are some tips to solve common problems when installing or using cViewIMAGE:

    1. Elevated Administrator: On your Windows 7 machines and later Operating systems, please register the cViewIMAGE.dll file using Elevated Administrator (Command line utility / Right click / Run as Administrator). This is because even the normal Administrator user on that operating system and later does not have the full set of rights but needs the elevated rights.

    2. The COM datasource: When creating a formula, the COM datasource that cViewIMAGE uses is listed under Datasources or More datasources in the Crystal Formula Editor. If you cannot see COM listed, either re-install Crystal and tick the box that asks if you want the COM option or else copy the driver from our Drivers file. Which driver you use eg depends on your operating system and version of Crystal.

    3. Folder location for driver: The COM data driver eg or P2smon.dll needs to be placed in different folders depending on whether you have 64 bit or 32 bit and also what version of Crystal you have.

    4. Appropriate location: Files such as the license file or the driver etc which needs to be placed in the folder appropriate for your Operating system or version of Crystal eg:
    a. The same location as cViewIMAGE.dll for Windows operating system 7 or later
    b. or in Program Files (x86) / cViewIMAGE if you have a 64 bit machine
    c. or in Program Files / cViewIMAGE if you have a 32 bit machine.

    5. Location of Images: If they are local on your development machine, there will also need to be a copy local on your user machines.

    6. Network permissions: To troubleshoot when your images are on a network folder, please move the images temporarily to a local drive eg c:\, If that solves the problem, we know it is a network issue - probably related to the user not having sufficient permissions for cViewIMAGE to access the network folder. (This will involve changing the formula which builds up the path so cViewIMAGE can find the images on your local drive)

    7. Deploy on another machine: If you want to deploy cViewIMAGE on another machine you will need to install and register cViewIMAGE.dll on each machine. These files can be in any local folder on your machine.

    8. License file: Each machine running cViewIMAGE will need the “license.xml” license file you received when you purchased cViewIMAGE for that machine.

    9. Register: cViewIMAGE needs to be registered on each machine that uses it eg depending on your operating system RegSvr32 "c:\Program Files\cViewIMAGE\cViewIMAGE.dll"

    10. Speed. If the images are on a network drive, the report will run a lot slower. Remember also that the user must have permission to access the folder of images.
    11. Memory: As cViewIMAGE is trying to move the images to the local machine, check whether memory on individual machines might be a bottleneck.

    12. Disc space: As cViewIMAGE is trying to move the images to the local machine for processing, check whether disc space on individual machines might be too small.

    13. Use a backslash: When building up the file location in your formula, remember to use a backslash eg c:\Projects\cViewImage\Demo v12\bette.bmp

    14. Quote marks: We have found that sometimes the formula building up the path contains quote marks not recognisable to Crystal, eg ones copied from Word or Outlook. Replace them with the double quote mark from the keyboard.

    15. File extension: Remember that the formula needs the file extension for the image eg .jpg or .bmp or .wmf or .png. Crystal does not support .giff and cViewIMAGE does not support .pdf. The extension needs to be included when building up the file path location in the formula used to point to the location.

    16. Conflicting dlls: There is a utility called Modules which may help your IT department to identify conflicts with dlls. You can search for & download this free utility from the Internet.

    17. Bar codes and fonts: Check whether there any barcode or other fonts that are installed on the working workstations but not on workstations that are having problems.

    Free Trial

    Customer Reviews
    Average Customer Review: Not yet rated
    Write an online review and share your thoughts with others.

    There are no reviews