MSSQL Invalid precision value

BIZ TMS Aurelius
1

I saw this reported in 2019 for NullableDouble, I'm hitting this issue with either plain TDateTime or NullableDateTime.

It's Windows 11 with no extra drivers installed, so the only one I can see shows as just "SQLServer", i.e.: it's probably not the "Native Driver". SQL Server is 2019.

The EXE is built in x64.

2

That's using native driver, BTW.

I could switch to FireDAC, but I'm not sure if just creating a single TFDConnection on the same ServerController is enough, or if I would need to do the TFDManager thing as well? - to keep it multi-user thread-safe.

3

Native Driver has fixed it.

1 Like