Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ODBC DSN must be 64-bit #46

Open
lunarindustrial opened this issue Oct 8, 2019 · 1 comment
Open

ODBC DSN must be 64-bit #46

lunarindustrial opened this issue Oct 8, 2019 · 1 comment

Comments

@lunarindustrial
Copy link

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.
@mhertzfeld
Copy link

Great catch. I have to wonder how many issues related to DB connectivity can be tied back to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mhertzfeld @lunarindustrial