Crsytal Reports for VS 2019 - 64 bit DSNs not listed

[former_member403137]

I am running Visual Studio 2019 Community edition and have installed CR for Visual Studio version 13.05.3805. I have removed all previous versions of Crystal reports for VS as well as the runtimes. I can view the reports in VS but when I try to set the data source location for a report to the DSNs that I created they are not listed. For the DSNs, I created two 64 bit DSNs using the MySQL connector tool. One is ANSI and the other is Unicode.

It was my impression that this version of Crystal reports for Visual Studio supported 64 bit connections but it doesn't look like that is the case. If 64 bit connections are supported, then why would I not be seeing the DSNs? If this is not true then does that mean I have to install a 32 bit version of MySQL server just to get Crystal Reports to work with Visual Studio?

Thanks for any input you can provide.

[former_member11696 · Accepted solution]

Hi Steve,

You are using SP 5 which is very old, first thing to do is use the latest SP 30 from here:

https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

See the Blog to help you upgrade your Project also.

Visual studio is a 32 bit application so it uses 32 bit DSN's.

When you compile for x64 then on the deployment PC create the same 32 bit DSN as you did on your DEV PC and it will work for you.

CR runtime is for your platform and not the OS

Don

[former_member403137 · Accepted solution]

Hi Don,

Thanks for the quick reply. I did not know that VS 2019 was a 32 bit app. That was a surprise to me. I had assumed it was 64 bit.

The download I used when I installed CR for VS earlier today was CRforVS13SP30_0-10010309.EXE which is the service pack you mentioned. It was not SP5 so I did not have to upgrade the service pack.

I created a 32 bit ODBC connection to the MySQL database I'm using and was able to reference it when changing database location for the report. Ran the report in preview mode and it all worked fine.

Thanks again for your help,

Steve