Bug #913 Fatal Error on creating project
Submitted: 24 Jul 2003 13:49 Modified: 6 Oct 2003 12:28
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
Category:Connector / ODBC Severity:S4 (Feature request)
Version:MySQL: 4.0.12, MyODBC: 3.51.05 OS:Windows (Windows 2000 SP4)
Assigned to: Bugs System CPU Architecture:Any

[24 Jul 2003 13:49] [ name withheld ]
   I have a fata error when creating new project using MSVC .NET. Projetc's settings: MFC application, using ODBC database (MyODB). It works normally with all another ODBCs. 

How to repeat:
   Run MSVC .NET, New project -> MFC Application -> SDI -> With Database Support -> ODBC -> select any MyODBC driver -> Finish -> Error

Suggested fix:
  none :(
[24 Jul 2003 14:59] [ name withheld ]
here is end of log-file:

devenv          53c-508	ENTER SQLDriverConnectW 
		HDBC                060915E8
		HWND                00000000
		WCHAR *             0x1F7B2690 [      -3] "******\ 0"
		SWORD                       -3 
		WCHAR *             0x1F7B2690 
		SWORD                        8 
		SWORD *             0x00000000
		UWORD                        0 <SQL_DRIVER_NOPROMPT>
[24 Jul 2003 15:19] MySQL Verification Team
Thank you for the bug report. I was able to repeat.
[6 Oct 2003 12:02] Venu Anuganti
Hi !!

I had a time to check this with .NET; and I could able to reproduce this. Though am not getting any crash from driver, but its coming from driver manager(I noticed this by attaching the VC.NET itself directly with driver, and debugging from driver directly ..), and I need to debug this further to see what exactly is happing.

Surprisingly using the same VC.NET, the database project stuff(New project->Other projects->Database project and then select MySQL ODBC 3.51 Driver DSN) works fine for all table manipulation, but it fails only with MFC support.

Stay tuned for further feedback..

[6 Oct 2003 12:28] Venu Anuganti
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Ok, this is fixed now, and the fix will be available for 3.51.07.

Thanks for the bug report