MySQL Bugs: #27432: Is this ODBC error

Bug #27432	Is this ODBC error
Submitted:	26 Mar 2007 6:47	Modified:	27 Mar 2007 12:24
Reporter:	bala krishnan	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.14	OS:	Windows (Windows XP )
Assigned to:		CPU Architecture:	Any

Description:
While Multiple users executing exe of VB with MySQL as database, following
error occurs during middle of processing.
I can't find what type of error it is.Whether this error is DB related or OS
error or MySQL connectivity errror.

Error signature

AppName:posting_inhousekeyverify2.4.exe AppVer:0.0.0.59 ModName:myodbc3.dll

ModVer:3.51.14.0 offset:0000d3c7

Reporting details

This error report includes: information regarding the condition of DATA CAPTURE when problem
occured;the operating system version and computer hardware in use;your Digital Product ID,which
could be used to identify your license; and the Internet Protocol (IP) address of your computer.

We do not intentionally collect your files,name,address,email address or any other form of personally
identifiable information. However, the error report could contain customer-specific information such as
data from open files. While this information could potentially be used to determine your identify, if
present, it will not be used.

The data that we collect will only be used to fix the problem. If more information is available, we will tell
you when you report the problem. This error report will be sent using a secure connection to a database
with limited access and will not be used for marketing purposes.

How to repeat:
The exe closes while this error occur, after that the exe may open and execute successfully. This error occurs twice or thrice before completing execution.

I tested it by using myodbc 3.51.13 and myodbc 3.51.14, but no solution found.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Hi.
If you look closely in your report you will *NOT* find any usefull information... I am unable to help.