Article ID	2174
Article Title	INFO: Crystal reports from CrystalReport and cCrystal in the same app
Article URL	http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2174
KBase Category	Crystal Reports
Date Created	09/26/2005
Last Edit Date	09/26/2005

Article Text
QUESTION:
Is it possible to have a Visual DataFlex 11 application containing RVs created to use CrystalReport class and RVs created to use cCrystal class?

ANSWER:
Yes. Report views using the old CrystalReport class and the new cCrystal (RDC) class can co-exist.

The only requirements are:
- The machine has Crystal Reports XI Developer Edition OR the RDC components installed  

- crpe32.dll (from Crystal Reports XI) is in the application's Programs directory -- for old reports to work.
What this really means is that crpe32.dll needs to be where it can be found by the calling program (in this case, the Visual DataFlex application), because the Common Files folder for the Crystal components doesn't qualify. Based on our experience, we recommend the Programs folder of the application workspace because it is the least potentially intrusive place to put it (i.e. it doesn't require "polluting" System32, your Bin folder or adding its location to the machines PATH).

- Put the appropriate crpe32 resource file (for instance, crpe32_res_en.dll) in the same location as crpe32.dll



We are not recommending that you continue to use the old interface (as it is unsupported by Business Objects, so we can't support it either). If you feel you *must* use this technique to aid transition to the RDC, we strongly recommend that you view that transition as a critical item that should be accomplished as quickly as possible.



Contributed By:
Marcia Booth
Company: Data Access Worldwide
Web Site: http://www.dataaccess.com


Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2024 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.