Common misses using Crystal Reports on 64 bit machine

[Former Member]

Purpose

To know about common misses using Crystal Reports on 64 bit machine.

Overview

Crystal Reports is a 32 bit application and when executed from a 64 bit machine there are certain constraints which need to be considered. Due to some misses on these constraints we might land into some abnormal behaviors.

The DSN used should be a 32 bit System DSN

Following are the steps to locate the 32 bit odbcad32 administrative tool to create a DSN.

Windows key plus Letter ‘R’ >> You can type in %windir%\SYSWow64\odbcad32.exe

Or you can navigate as follows

My Computer >> C drive >> Windows>> SYSWow64 >> odbcad32.exe

The WOW64 feature provides the libraries necessary for the apps themselves to run in native mode, plus it provides the required registry and file location redirection. On the processor level the binaries also execute natively.

Making changes to the registry

For any kind of changes in the registry one should look under the WOW6432node.

When the user needs to increase the size of LOVs in Crystal Reports and the application is running on 64 bit machine then following is the location to be looked into

*Before making any changes to the registry it’s a best practice to back up the registry.

If it’s Crystal Report 2008 it will be

HKEY_LOCAL_MACHINE >> Software >> Wow6432Node >> Business Objects >> Crystal Reports >> Database Options >> and out here you need to create LOV key under which a string key needs to be created ‘MaxRowsetRecords’.

For Crystal Reports 2011 it will be under SAP Business Objects >> Suite XI4.0 >> Crystal Reports >> Database Options >> here you need to create LOV key under which a string key needs to be created ‘MaxRowsetRecords’.

I hope the above mentioned locations would be helpful.