When converting a Common Language Runtime (CLR) Decimal data type to a JADE Decimal primitive type in earlier releases, the wrong value was written to a JADE property from a .NET or ActiveX decimal if the value contained 29 significant digits. The algorithm used to round a decimal value was wrong if the value of the number represented in the significant digits, ignoring the decimal point, was greater than or equal to 2^95 (39,614,081,257,132,168,796,771,975,168), which affected .NET and ActiveX decimal values.
Appendix A of the JADE .NET Developer's Reference stated that when converting a CLR decimal data type to a JADE Decimal primitive type, there may be an overflow or data loss saving data to the database. From JADE 7.0.11 and 7.1.07, this is no longer true. If necessary, JADE rounds decimal values on assignment to the number of decimal places defined on the property.