my project -> property -> SQL -> OpenESQL -> <ADD> -> Select <DBMAN> ->  After that, I can't select ODBC, so I can't use ODBC.

Although it appears that you can't select ODBC (in the Add Directive dialog), go ahead and click OK to add the directive. It will add the DBMAN directive with its default value of ADO. Once it's been added (and the Add Directive dialog has closed), you should be able to change its value to ODBC. In other words, it takes two separate steps: first, add the directive with its default value, and then change the value. 

Also, in order to use the OpenESQL Assistant with ODBC, you may need to change the mode from ADO to ODBC. Go to Tools -> Options -> Micro Focus -> OpenESQL Assistant, and in the right pane under General, change the mode from ADO.NET to ODBC.

I hope this gets you one step closer!

Thank you.

I just wanted to ensure that you are using the correct project type here.

If you select DBMAN in the SQL tab and the default option is ADO then this is a managed code .NET project. If you were using a native project then ODBC would have been the default.

What is your desired project type and your development plans?

If you are using VC to learn the COBOL language then I would recommend that you create a native project and use ODBC.

If you wish to use the new OO syntax and create .NET applications that use Windows Forms, ASP.NET, WPF, etc then you will have to use a managed project type.

Managed projects should use ADO and not ODBC as ODBC is a native technology.

You can still use ADO with MySQL but you would have to connect via connection string instead of using a DSN created with the ADO Connection Editor.

I believe that the support for MySQL may be improved in VC 2.3 but I do not currently have MySQL installed to test this.

Thanks.