Win2K, MsSql2K, IIS5, etc.
I have HTML forms which do a POST to Python/ASP pages which call my .py class which uses the "standard" ODBC module to insert a record into MsSQL.
This particular app is an online timesheet app: enter timecharges to jobs, administrator reviews/approves/exports, etc.
The UnitsCharged field is a float. The HTML form limits entries to 3 chars, entries are typically "1.2" or "0.7" or "4", etc. Everything goes in fine, when you view the results via ASP they look fine.
But when you do a direct (SQL Query Analyzer) query into the table you see values sometimes like 0.69999999999999996, etc. (while others work out just fine).
I figure this is probably a binary/decimal conversion problem, right? But it makes me nervous to have nasty data in there, I'm afraid it will bite me in the ass sometime (someone will see an ugly value someplace, and it will undermine the credibility of the system). Is there anything I can do about this? Change the field type in SQL? Use a different SQL module? Or do I just hold my nose and live with it?
