Devart Forums

1) Once you generate a dataset using the wizard, I'm coming up with an error in visual studio 2008 dragging and dropping tables from the server explorer to the dataset.

Receiving error: Mouse drag operation failed
The specified identifier has too many parts. Parameter name: other.

2) The wizard isn't auto generating the one to one relationships from my database. Is this intended? (Basically, the primary key column is the foriegn key column for the child table. )

I just now noticed that there is an Add table in the edit dataset window. However, this icon is grayed out. If I could enable it, then it would solve the adding table problem.

Could you post the full name of your OS?
Send me (alexeyman*crlab*com) the tables definition script please.
DataSet wizard should regenerate all table constraints.

The first problem is being fixed now.

Alexey.mdr wrote:Could you post the full name of your OS?
Send me (alexeyman*crlab*com) the tables definition script please.
DataSet wizard should regenerate all table constraints.

The first problem is being fixed now.

Glad to hear the first problem is being addressed. I'm using windows xp pro with Visual Studio 2008

I have emailed you the table definition script.

I've not received your email yet.
Could you please send it again to alexey*crlab*com and CV to mysqlnet*crlab*com?

Alexey.mdr wrote:I've not received your email yet.
Could you please send it again to alexey*crlab*com and CV to mysqlnet*crlab*com?

I have resent the email. I had sent it under my gmail account:

But just in case you dont get it, here it is:

CREATE TABLE `Meridian_dbo`.`AdminCharge` (
`ChargeID` varchar(64) collate utf8_bin NOT NULL,
`Card#` varchar(50) collate utf8_bin default NULL,
PRIMARY KEY (`ChargeID`),
CONSTRAINT `FK_AdminCharge_Charges` FOREIGN KEY (`ChargeID`) REFERENCES `Charges` (`ChargeID`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

Also, do you have a time frame when the adding tables feature will be implemented / fixed?

Thank you for the bug report.
We have reproduced the problem.
This bug will be fixed in the next build.

Alexey.mdr wrote:Thank you for the bug report.
We have reproduced the problem.
This bug will be fixed in the next build.

Is there a time frame you can give me?

Thanks Alexey.

We plan to issue a new build approximately in two weeks.

Alexey.mdr wrote:We plan to issue a new build approximately in two weeks.

To clarify, did you say both problems will be addressed in the next build?

The time frame sounds good. Thank you.

We will make everything possible to solve both problems in the following build.

Alexey.mdr wrote:We will make everything possible to solve both problems in the following build.

Alexey,

I'm wondering if you can give another estimate on the release date for the patch that includes these fixes.

Thanks in advance.

The bugs are fixed now (internal numbers CR 26544 and CR 26898).
Now we are testing the new build.
The release is scheduled to be issued on the coming Friday (April, 18 ).
Thank you for your patience.

Alexey.mdr wrote:The bugs are fixed now (internal numbers CR 26544 and CR 26898).
Now we are testing the new build.
The release is scheduled to be issued on the coming Friday (April, 18).
Thank you for your patience.

Thank you.

The new build is available for download now.