ODBC 18 Driver - Invalid Argument for Database

[procedemis]

Using ODBC 18 driver with an existing report [that runs fine when using ODBC 17 driver] on Crystal Runtime SP35 - the report will not work.  It returns 'Invalid Argument for Database' error and several other errors in the log.

I have enabled Crystal Logging and attached the file to this post.

Does anybody have experience troubleshooting using the log files?

We have opened the report in Crystal Designer 2020, re-set the data source, verified the database, etc and the report runs perfectly from the designer... but when we run it from our application which targets SP35, we get the attached errors.

I have submitted a post recently about ODBC 18 Driver not working from the designer, but new patches have fixed that issue, so I wonder if there were changes made in the designer, that have not been applied into the runtime yet.   Is there a 'beta' version of the Crystal Runtime that just hasn't been released yet to try, as SP35 was released in 2023 [before the designer fixes were even applied]

[DonWilliams]

Hello,

I have it now, thank you for the logs and report.

The report works for me.

I'm not sure why, older SP's would catch the error when a reserved character was used in a formula name, in your case it's the Parameter that has the character in it, but still applies.

See this KBA:

2042551 - The following characters are reserved for internal use only in Crystal Reports Designer formula names - ‘@’,’?’,’{‘,’}’

It could be because of the history of the report:

Try renaming the Parameter without the @ in it's name and see if that works for you.

Since the .NET SDK log does catch the error, CRD is more forgiving since it's a Design tool so it can deal with errors on the fly and work around them, SDK can't, it assumes the report is 100% valid:

2024-3-28-13-15-23 10164 ..\cserrinf.cpp 523 Error 31853 (..\..\src\data\datainterface.cpp, 7889): Invalid Argument provided.: 1

2024-3-28-13-15-23 10164 ..\cserrinf.cpp 523 Error 31853 (..\..\src\data\datainterface.cpp, 7889): Invalid Argument provided.: 1

But, I'll send the zip file over to R&D and see what they say.

Don

[procedemis]

We just tried it with renamed parameter and still get the same error. Yeah, the report works from the crystal runtime [with both @ in parameter name or without] if we use ODBC 17 - only breaks with ODBC 18. Appreciate you and the time you've spent looking at this w/ us.

[DonWilliams]

What is the url to the one you posted for CR Designer?

And yes, since CR for VS only releases SP's every 6 months or so they may not be in sync.

And no there will not be a patch, never has been, for CR for VS. The fix will likely be in SP 36 but to confirm this I can check with the Developers but need details about the fix you got for CR Designer.

Can you run the same report in CR Designer and attach the CRLogger log file so we can compare them?

[procedemis]

Here is the previous issue I reported, when Patch 100 for CR 2020 designer came out the problem went away, so not sure what was done.

The error I am reporting in this post is not the exact same issue.   I am not sure what was done to 'fix' ODBC 18 issues from the designer, but after patch 100, the same report runs perfectly from the CR 2020 designer, so I guess I only hope the same type of fix is applied to the runtime also.

https://community.sap.com/t5/technology-q-a/odbc-driver-18-for-sql-server-w-force-encrytpion-option-...

[DonWilliams]

R&D has confirmed there were updates that CR for VS did not get yet. Is it possible to get a sample report with demo date? You can import Extreme.mdb if you have it and use it to duplicate the issue. A report with saved data may be enough for them.

[procedemis]

@DonWilliams, I have PM'd you the files you requested... just want to make sure you saw that 🙂

[DonWilliams]

Got them, I sent the file to R&D last week, sorry I forgot to update you.

There was one fix they did and not ported into CR for VS.

He says it will be in SP 36, not sure when it'll be released, likely in June but may be sooner....