Interaction w/ MySQL !!

Greetings,
I am attempting to make a windows application that among other things allows the user to view tables and edit their contents in a MySQL database. I'm using VS 7, and i'm getting problems with the following. I add in a new dataset to my project, in the development window it says drag components in this window from either the toolbox or the server browser. Well I have the MySQL database I want to edit active in the server browser. I drag the appropriate table I need to edit into the window and I get an error saying my data adapter type doesn't support ODBC. Even getting VS to connect to my database was a hassle, I downloaded the MyODBC driver, and added in the ODBC manager (control panel/administrative tools) as a system wide data name, and when i go into VS and ->add connection, the provider list only shows OLE DB providers. there's a OLE DB provider for ODBC drivers, so I select that ad it can read and even view / query the tables in my db. But whenever I try to add the tables to a dataset it is giving me ODBC compatibility issues. If someone can at least tell me if it's possible in VS/VB to allow people to interact with a MySQL database I would very much appreciate it ! this is really driving me crazy.
[1246 byte] By [Helios] at [2007-12-16]
# 1
Why don't you try the MyOLEDB driver directly and not the MYODBC?
papadi at 2007-9-9 > top of Msdn Tech,Visual Basic,Visual Basic General...
# 2
Support for ODBC DataAdapters was added in VS.Net 2003 so prior to that you would need to use the OleDB for ODBC driver. When doing drag/drop from the Server Explorer we attempt to generate an OleDB DataAdapter that uses the managed OleDB provider under the covers. We should still be able to talk to the ODBC driver but most of that communication is predicated on the ODBC provider supplying us with certain pieces of information. It is possible that the MyODBC driver does not provide us this information and thus causes problems in the designer.

You may want to try instancing an OLEDB Data Adapter in code rather than through drag/drop on the designer. This should give you a better indication of whether the scenario you describe is possible.

KrisLa_MS at 2007-9-9 > top of Msdn Tech,Visual Basic,Visual Basic General...