Bug #67070 Visual Studio Connection
Submitted: 3 Oct 2012 22:48 Modified: 8 Oct 2012 9:18
Reporter: Geoff Wootton Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version: OS:Windows (Windows 7)
Assigned to: Bogdan Degtyariov CPU Architecture:Any

[3 Oct 2012 22:48] Geoff Wootton
Description:
Hi 

I am trying to create databse program using Visual Studio 2010 and using a MySQL database that I have created with the latest version of MySQL community version. My problem is Visual Studio keeps crashing. I have tried my best to explain the problem step by step as follows. 

I'm using Windows 7 and have installed the MySql ODBC connector

Thank you

How to repeat:
1. In Visual Studio go to File->New Project Select MFC Application. Enter a name for application in Name box and click OK 
2. Click next until you get to Database Support. Select Database view with file support and ODBC under Client type: Then click Data Source button 
3. In Select Data Source Dialog click New 
4. In Create New Data Source Dialog scroll down and select MySQL ODBC 5.2w Driver. Then Click Next 
5. Type in the name you want to call your data source and save it 
6. Now MySQL Connector/ODBC Data Source Configuration dialog box pops up. Enter TCP/IP Server, User, Password, Select database and click Test. Test result dialog says Connection successful. So far so good 
7. Now the first problem pops up. A Create Data Source dialog box saying The File Data Source was not saved. 
8. After closing previous dialog box your saved .DSN appears. Select it and click OK 
9. The MySQL Connector/ODBC Data Source Configuration Dialog box reappears with all fields filled out. Click OK 
10. The Select Database Object dialog now appears showing your tables. Select the table you want and click OK 
11. Your now back to MFC Application Wizard. Click finish and then the fun begins 
12. Visual Studio crashes saying a problem has been encountered and then Visual Studio shutdowns and restarts
[3 Oct 2012 23:34] MySQL Verification Team
Thank you for the bug report. Why do you think the crash of your Visual Studio is MySQL bug and not the VS itself?. Thanks.
[4 Oct 2012 1:27] Geoff Wootton
Hi

Thank you for replying

I'm sure where the problem lies and may very well not be MySql but Visual Studio.

This is kind of what I am trying to find out. I can connect to other databases i.e Access with no problems.

Thank you for your help
[4 Oct 2012 2:22] Geoff Wootton
Sorry. The first line of my reply should read

I'm not sure where the problem lies and may very well not be MySql but Visual Studio.
[4 Oct 2012 23:06] MySQL Verification Team
Thank you for the feedback. Are you using the Connector ODBC 64-bits? If yes try the 32-bit package (just a guess). Thanks.
[4 Oct 2012 23:22] Geoff Wootton
Hi

I'm using the lastest version of the 32bit ODBC connector
[7 Oct 2012 1:20] Geoff Wootton
I think I have the problem solved. It seems to work with the latest version of Visual Studio

Than you  for all your help
[8 Oct 2012 9:06] Bogdan Degtyariov
Verified.
[8 Oct 2012 9:08] Bogdan Degtyariov
Initially I thought it might be because of using the file DSN.
However, using system DSN causes the same crash.
[8 Oct 2012 9:11] Bogdan Degtyariov
The Windows Application Log has the following details that point to VsWizard.dll rather than myodbc5w.dll:

Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: VsWizard.dll, version: 10.0.30319.1, time stamp: 0x4ba1fde1
Exception code: 0xc0000005
Fault offset: 0x00032edd
Faulting process id: 0x20e4
Faulting application start time: 0x01cda5340eba780f
Faulting application path: D:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: D:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\VsWizard.dll
Report Id: 8d7ea45e-1127-11e2-906b-005056c00008
[8 Oct 2012 9:18] Bogdan Degtyariov
Not our bug.