Background: we have recently had our Test environment updated to v14. This means our SQL Server is now version 2016, and Infomaker is 12.6.
Since we were previously on SQL Server version 2008, I’ve been expecting some compatibility issues with our older custom code, particularly procedures backing old custom reports. I’d sorted through one issue, but now there’s a second with a very old, but unfortunately heavily used, custom report. For certain parameters, the report crashes with this error:
SQLSTATE = 22003 Microsoft OLE DB Provider for SQL Server The floating point value '2.121995814680423E-314' is out of the range of computer representation (8 bytes).
SQLSTATE = 22003
Microsoft OLE DB Provider for SQL Server
The floating point value '2.121995814680423E-314' is out of the range of computer representation (8 bytes).
I assumed this was another SQL incompatibility, although the number it was reporting really shouldn’t ever be getting generated.
The report is pretty ugly: about 10 procedures of poorly written SQL and about as many different Infomaker data windows to dig through. However, passing in duplicate parameters directly into the procedures produced no error messages. Passing the parameters into Infomaker did, so I started working my way through the datawindows to figure out where the error was bubbling up from. However, my trial died oddly in a datawindow that does not actually invoke and stored procedures: it’s rather the overall framing for a set of child datawindows, and simply passes the parameters down to them. The child datawindows do not generate the error on their own and the datawindow in question doesn’t seem to do any processing of any kind, not even any “expressions” (I’ve looked through all of the elements in the datawindow for anything like that).
I’m stumped: does any of this sound familiar to anyone?