My client has data that they review using MS Excel. For two records, the property block/lots were forcibly turned into scientific notation. I tested the issue myself, and saw the two bad fields. So I rendered the query in SSMS, set the destination columns in MS Excel 365 to TEXT, and copied the data into the text-formatted columns. It still forced those two fields into scientific notation. If I simply changed the fields to text, it didn't change the data back to its original format - it left them in scientific notation. I also tried to cast them on the SQL side as specifically text fields (though they already were text), but that didn't help either.
The two fields are:
5428E-028 was changed to 5.43E-25
0436E-022 was changed to 4.36E-20
These are automated reports that the users view in a reporting tool and download automatically into MS Excel. This seems like a bug to me. I had to manually fix and send them the report, which isn't a great solution.
Is there any way to catch this problem before it reaches the client?