Once we had it we were able to get to the DLLs.
We not only had to upgrade the runtime to 64 bit versionwe also had to add references to the dlls removing original references from the code. We just recently upgraded a similar application that was using old crystal dlls. Do I need to set the database name in the code? Seems weird that that would be the answer and it has worked for years. The server name field is filled in but disabled, and the database field is disabled but not filled in. This is a really old application and has run for years The login ID and password are being set in the code.
Uninstall the runtime and install the bit version instead. The village of mentuccia, municipality of montefiascone (vt) lazio I suspect you have a bit application and you've installed the bit runtime. You would then install the version of the runtime that matches the bit-ness of the application. When determining which "bit-ness"to install for the runtime, you need to look at the application, NOT at the computer where you're installing it. I am not having an easy time navigating the SAP site to find noteonce I do I will let you know what happens. On the users computers they don't have crystal reports installed, just the runtime. Now I am going to start over and see what changes I made are needed and which ones are not needed. The reports had been created with an OLE db connection, I changed a couple of them to Oracle server connections and was able to run them in our application. As I had said the cr reports are sitting on a file share.
I finally got it to work, I had to change the database connection type in the crystal reports the application is running. When you get to the download page, the orange button gives you the integration with VS and the blue buttons are links for the various runtime installs that are available.
That page also contains links to the site where you can download the SDK. If you look at the wiki hereit will tell you what changes need to be made. Also, there have been a few changes in the way some things are done with the SDK nothing major. If you need to upgrade to a newer version to work with a newer OS, you will need to recompile your application with the SDK version that you're going to use to deploy. One of the tricks for getting applications written with the SDK to run properly after they've been deployed is that you must have the same version service pack of the SDK installed in VS and on the target machine when you deploy your application.
This version doesn't support Windows 10 if that's where you're installing it, although you might be able to use the Compatibility Troubleshooter to set the application to run as if it were on an earlier version of Windows. What OS are you installing it on? In the initial question you mentioned that you had been using the This is for service pack 3.
Either the Crystal Reports registry key permissions are insufficient, or the crystal Reports runtime is not installed correctly It does have the server name field is filled in but the Database name is blank. I am trying to install our production application on a 64bit computer, our users computers up until now have been 32bit.