I have an application built using VS 2010, and the matching crystal reports. However, the application includes legacy VB 6 components, and they are also used to generate reports.
Up until now everything has been fine, and the setup kits we build distribute the single crystal runtime required. Now I have discovered that CR 2010 does not allow us to distribute the activex viewer, crviewer.dll, and it isn't installed with the runtime.
I have spent a huge amount of time updating the vb6 projects to reference crviewer.dll version 13, since it is supplied with Crystal for VS 2010, only to find out that we are not allowed to use it
If we're not allowed to distribute it, and the runtime doesn't install it, why do we have it?
What workaround can anybody suggest? I don't really want to have to distribute 2 runtimes (2008 and 2010), and I don't want to have to undo all the changes I've made to the vb6 stuff (this really is write-only code).
Unfortunately, the answer I have for you is most likely one that you do not want;
Lots and lots of info on the RDC and VB6 and .NET on this web site (use the search box in the top right corner of this web page). There are KBs, Wikis and Blogs that I personally created. In a nut shell, the RDC was retired in version CR XI R2 (11.5). E.g.; two versions ago. While you will find the crxddrt.dll and crviewer.dll included with CRVS2010, these are for internal purposes and you are not licensed to use these (craxddrt.dll was a special license only in any version of CR). Your only option is to rewrite the code using the CR .NET SDK. As for the resources available on this website. See the following small sample;
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]