We are attempting to develop a custom application using .NET/C# and the Crystal Reports runtime, sourced by Salesforce. We have experience with developing such solutions with various drivers, however this is our first attempt at SF.
My question: Has anyone been successful in writing a custom .NET application with *any version* of the Crystal runtime with Salesforce with *any version* of Visual Studio? I apologize ahead of time if I missed any threads but I have been unable to find any information on this; only found:
I found one possible resolution for 2008 here, assuming this is runtime install for VS2008: http://scn.sap.com/thread/1509991 ??? (haven't tried this yet.)
The driver released with the Crystal 2008 *designer* works perfectly, so I assumed the SF driver would be available in the latest runtime.
I downloaded the Crystal 2011 Designer evaluation and after struggling to connect to SF at first, I was able to resolve the designer connectivity as described in this thread, by replacing the jar files:
I then installed Crystal for VS 2010 runtime 13.0.4 on a fresh virtual image with *ONLY* VS2010 installed (ie, No Crystal 2008 or 2011 Designer, and no runtime of an older version); alas, there is no driver for SF installed!
I realize this was a long shot but I then copied the CR2011 sforce* dll’s into the runtime directory (C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86). The VS2010 wizard recognized the salesforce driver, but crashed immediately when I tried to create a connection. I then tried to copy a report into my solution folder created with the 2011 designer; as expected, VS2010 crashed on opening the solution.
An SAP sales representative suggested I post on this site.
(Please don't respond with alternative product pitches - DBAmp, CrystalReports.com, Crystal Server, Progress Software ODBC driver, etc. We are trying to cut costs like everybody else.). If I can't figure this out I will be resorting to scripting the SF data loader to SQL Server if possible.