Symptom
The Pervasive database requires a 24 byte encryption key to get 128 bit encryption which many of our customers want. However, the password field in Crystal Reports is only 8 bytes long.
Environment
- Crystal Reports 2008
- Crystal Reports 2011
- Crystal Reports 2013
- Crystal Reports for Visual Studio SP 16
- Pervasive 11
Reproducing the Issue
To view a table with info in Pervasive's Work bench you would query the DB this way as an example:
SET OWNER = '123CR2013123456789012' ;
set ansi_padding=off ;
select * from "DEMODATA"
Check the Pervasive help file on configuring Security
Resolution
This issue has been assigned to R&D to review and resolve.
In Cystal Reports Designer the password length will be increased to allow enting in a 24 bit encrypted password.
In Crystal Reports for Visual Studio this will work by setting the Password value in the log on info in both the ReportDocument ( Engine) and ReportClientDocument ( RAS )
CR for VS SP 16 should have the fix.
Yet to be determined which version of CR Designer the update will be in.
Keywords
Pervasive, password, encryption, Crystal Reports, crystal reports for visual studio, crfor vs, .net , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Problem