![]() So my question here is two-fold: 1) Does anyone know whether this issue I am having is a Windows Installer issue or is it specifically a Crystal Reports issue? 2) How can I specify in the Visual Studio setup project that the 32-bit version of the Crystal Reports runtime should always be installed, even when installing on a 64-bit machine. If I manually go install the 32-bit version of Crystal Reports runtime then the reports work correctly, but I want the install of Crystal Reports to work correctly from the application installation. The application then gives an exception when you try print a report because it needs the 32-bit version installed. Installing on 32 bit machines give no problem, but when I install on a 64-bit machine for some reason the installer installs the 64-bit version of the Crystal Reports Runtime Engine. ![]() odbcdao) with 32-bit in your Crystal Report DataSource It is also strange that you already installed 32-bit and 64-bit CR runtimes, why you installed CR versions for visual studio I had a similar problem as yours, but after replaced 32-bit MDB and DAO with DataSet, everything becomes fine. Also Windows Installer 3.1 is checked as a dependency. Do you have any data source or connection (e.g. I have SAP Crystal Reports, version for Visual Studio (version 13.0.13) installed on my development machine and in the setup project, under dependencies I have Crystal Reports Runtime Engine for. I have a Winforms application that is compiled for 32-bit (x86), which has a setup project that also targets x86.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |