This is a solved issue, but I wanted to share with the community.
We're using CR 2016 on a Windows 10 server. CR 2016 still requires ODBC 32-bit to run. However, CrystalReportsNinja requires a 64-bit ODBC DSN in order to connect via ODBC.
We were trying to connect to CR with CrystalReportsNinja via the 32-bit DSN setup for CR 2016, but it wasn't working. We setup a 64-bit DSN just for CrystalReportsNinja.
This is a solved issue, but I wanted to share with the community.
We're using CR 2016 on a Windows 10 server. CR 2016 still requires ODBC 32-bit to run. However, CrystalReportsNinja requires a 64-bit ODBC DSN in order to connect via ODBC.
We were trying to connect to CR with CrystalReportsNinja via the 32-bit DSN setup for CR 2016, but it wasn't working. We setup a 64-bit DSN just for CrystalReportsNinja.