![]() I also looked at the INI Files that ODBC creates and everything. Then we recreated, reconfigured and retested the system DSNs. So the first thing I checked was that we were loading ODBCAD32.exe to add the new system DSNs. The odd part was that one existing system DSN DID show up in CR, but any new system DSN would not show up. If he added a new “system” DSN he could not see it. ![]() The user was creating DSNs but CR could only see the DSNs if he added it as a “user” DSN. Today after helping a customer I learned a few more strange things about the ODBC Administrator that can get confusing. A couple of years ago I wrote about this. But in Windows 7 and later you are taken to the 64-bit Administrator by default. All versions of Crystal Reports up to v14.2 (2016) need to use the 32-bit ODBC Administrator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |