Bug #26149 | Problem with AVG() function | ||
---|---|---|---|
Submitted: | 7 Feb 2007 14:45 | Modified: | 12 Feb 2007 16:52 |
Reporter: | Gabriele Franzoso | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51.11-2 | OS: | Any (All) |
Assigned to: | CPU Architecture: | Any |
[7 Feb 2007 14:45]
Gabriele Franzoso
[12 Feb 2007 9:51]
Tonci Grgin
Hi Gabriele. Please do not: - Submit reports on old versions. Upgrade first. - Submit report more than once. I will point you to my last post in Bug#18157 which should probably solve your problem. Now, what is the exact error (and error number)? What happens when you upgrade (ADO, MyODBC, NET fw) to recent versions?
[12 Feb 2007 14:19]
Gabriele Franzoso
Thanks for your feedback! I have updated the ODBC driver and aligned to the latest Windows update. AVG() is now calculated correctly, however the exception in the Recordset is still there. The exact error number is not available to us; the only information we got from the system is: {System.Runtime.InteropServices.COMException} Despite the error above, we should now be able to use MySQL with our application - provided all the remaining tests will pass.
[12 Feb 2007 15:03]
Tonci Grgin
Hi Gabriele. Ah hmmm, that exception can mean anything... You would do good to investigate it. Anyway, glad I could be of assistance. Thanks for your interest in MySQL.
[12 Feb 2007 16:52]
Gabriele Franzoso
Thanks for the support and your quick response