Error when creating dataset using create dataset wizard

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
sportsoft
Posts: 4
Joined: Wed 20 Feb 2008 05:35

Error when creating dataset using create dataset wizard

Post by sportsoft » Wed 20 Feb 2008 05:43

Hi There

Please help very urgent (aren't they all)

We have been using mydirect 3.55 for quite some time now with out any real problems.

Upgraded to 4.30 due to the streaming capabilites now available with mysqldump as our databases a quite large. This all works fine in the new version.

I un installed the old version, and reinstalled 4.30, updated the references in VS to the new version and tested to make sure that the existing projects worked and they all do.

I tried however to create a new form with a new connection, dataadapter and then from the dataadapter use the dataset creation wizard (just as we always did with the previous version). It creates the dataset, but the dataset has the following errors:

Code: Select all

Error	42	Value of type 'CoreLab.MySql.MySqlConnection' cannot be converted to 'CoreLab.MySql.MySqlDataTable'.	C:\Development\Indoor System\Vb Apps\Indoor Server Version\DataSet_player_membership1.Designer.vb	281	52	Indoor Sports System
One for each data table

Code:

Code: Select all

Me.tablegame_type = New game_typeDataTable(Me.Connection)
The "me.connection" is a connection type and it requires a datatable type.

So as it doesnt require a parameter, I removed it and the errors went, but then the dataset is corrupted and it causes many many problems including VS to totally freeze.

I really need help with this issue as we have to fix some major bugs that require this feature to function correctly.

Nick

Alexey.mdr
Posts: 729
Joined: Thu 13 Dec 2007 10:24

Post by Alexey.mdr » Thu 21 Feb 2008 11:36

Please make a completely new WinForms project.
Run the DataSet wizard (create a new connection, use provider-specific code generator).
If you need your DataSet get filled by other than auto generated MySqlDataAdapter,
drag-and-drop a new MySqlDataAdapter. Specify the SELECT statement and the connection.
Try filling your new DataSet with the new adapter.
Do you still receive the error?

sportsoft
Posts: 4
Joined: Wed 20 Feb 2008 05:35

Works, but how do I move forward

Post by sportsoft » Mon 25 Feb 2008 10:09

Thanks for the reply.

That did fix the problem, but it really doest offer me a solution to the situation. Our project has hundreds of refences to the 3.55 version.

So how can we move forward with this project?

Nick

Alexey.mdr
Posts: 729
Joined: Thu 13 Dec 2007 10:24

Post by Alexey.mdr » Mon 25 Feb 2008 16:08

If you would like to move to version 4.30,
correspondingly change all the references in your .csproj files.
It should not be very difficult.

sportsoft
Posts: 4
Joined: Wed 20 Feb 2008 05:35

Still not working

Post by sportsoft » Thu 28 Feb 2008 00:49

I Have changed all the references in the project to the 4.3 version and still exactly the same problem.

Alexey.mdr
Posts: 729
Joined: Thu 13 Dec 2007 10:24

Post by Alexey.mdr » Thu 28 Feb 2008 15:34

I assume the problem is not in the version.
As MyDirect .NET installs policy files into GAC.
Please send me a small test project to reproduce the problem.
It is desirable to use 'test' schema objects, otherwise include the
definition of your own database objects.
Do not use third party components.
If it is impossible for you to create the test project, send us a piece of
your code where the error occurs.

Post Reply