Any ideas how to fix?
Partially fixed with backing down Crystal Reports to 32-bit after an upgrade to 64-bit got through, but still having problems.
How many thousands of custom reports are out there that are going to have to be modified for CSCOM then that wete working fine prevously? I will test out your theory with this one and see. I am suspecting a recent windows security update is the root cause of this
How do you get the company name at the top of your reports? ;)
I'm curious to see what you find.
How do you get the company name at the top of your reports? ;)
I'm curious to see what you find.
This particular report is just a payroll check advice. The company name is a graphic.
Changed my driver back to 18, added CSCOM to the main report, linked to the BKREG table. Same error:
Invalid argument for database. This is the same error the client has on their end. Both running a full install of Sage programs locally, both running Windows 11. There were a few windows security updates installed on my machine mid-February. I might try uninstalling them and see what happens
At this point it's just so much easier to install ODBC driver 17.
*Community Hub is the new name for Sage City