Reports with a Pervasive SQL database connection, created in an earlier version, when opened in Crystal Reports XI Release 2 Service Pack (SP) 2 and above behave differently, apparently caused by different synchronization.
Crystal Reports XI R2, 2008, 2011 and Crystal Reports Developer for Visual Studio
The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall the Microsoft Windows operating system. Use the Registry Editor at your own risk. It is strongly recommended that you make a backup copy of the registry files before you edit the registry. For information on how to edit the registry key, view the 'Changing Keys And Values' online Help topic in the Registry Editor (Regedit.exe).
1. Close all Crystal Reports applications.
2. From the Start menu, click Run.
3. Type "regedit" and click OK. This opens the Registry Editor.
4. Navigate to the following registry sub key:
CR XI R2:
HKEY_CURRENT_USER\SOFTWARE\Business Objects\Suite 11.5\Crystal Reports\Database
HKEY_CURRENT_USER\Software\Business Objects\Suite 12.0\Crystal Reports\Database
Note: this is not working in the .NET SDK - Issue has been tracked under ADAPT00010540
HKEY_CURRENT_USER\Software\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database
CR Developer for Visual Studio:
HKEY_CURRENT_USER\Software\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports\Database\QueryEngine
Note: this is not working at this time - Issue has been tracked under ADAPT00010540
5. Create a new key (right-click the Database key and select New > Key), named QueryEngine.
6. Create a new String Value (right-click the QueryEngine key and select New > String Value), named AllAtOnce_BackwardCompatible and with value of "1"
7. Close the Registry Editor.
pervasive, synchronization, synchronisation , 9937218 cr vs net , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Bug Filed