Reports with date fields produce a runtime error.

[SuperCoder]

Our app is used on hundreds of computers in California. There is one computer that encounters an error when the user tries to print a report with a date field. All other reports run fine. The error messages are all similar to the one below but the File description will vary with with which report is being run. All error messages say "A date-time is required here." at the bottom of the message.

Windows 10

.NET 4.7.2

64-bit version of CR runtime 13_0_32

VB.net

[ido_millet · Accepted solution]

Compare the database connectivity driver used on the "bad" computer to the one used on a "good" computer.
If the report uses ODBC, you can see the driver used in the ODBC DSN configuration dialog.

[SuperCoder · Accepted solution]

5 stars for you. The ODBC was configured with an out dated SQL Driver which does not handle DateTime2. Thank you so much.

[DonWilliams]

Hi Jeff,

CR dynamically generates the SQL based on the DB Client used.

It could be that one PC either doesn't have a client installed or it's a different version.

If could also be the User doesn't have rights to use the client or the software.

Try logging in as a local PC or Network Admin and see if that works.

Don

[DellSC]

Do you have any way of checking the database the user is connecting to? It looks like the trn_date field may not be a datetime - it might be just a date instead.

-Dell

[SuperCoder]

Yes, the date field is datetime. All of the computers in this office (share same database) can run date reports just fine except for this one computer. There is something about this computer that is preventing the reports with dates not to run. Any ideas.

[DellSC]

I would try uninstalling the runtime and re-installing in case what's actually there is an older version. IIRC, there were some problems with dates with one of the recent versions of the SDK.

-Dell