Problems on adding a new dataset using MySQL via ODBC

  • Thread starter Thread starter Vanessa
  • Start date Start date
V

Vanessa

Hi all!

I am using Visual Studio 2008 and I am having problems on creating a
dataset. I have a MySQL database accessing through ODBC. On adding a new data
source, when I try to select a table on the database it gives the following
error:

<`database`..`table`>
Could not get column information for database object named
'`database`..`table`'

Does anyone knows what is happening?

Thanks in advance,
Vanessa
 
Vanessa - there are a lot of potential issues related to column names. Is
there anything unique about it in terms of being a reserved word, having
spaces or characters or sosmething like that? That's usually a culprit.

If it's the case, then you can either change the column name in the db
(usually the wisest choice) or you can just create the dataset by hand in
the designer or just build it through code by declaring/instantiating a
dataset, then a datatable, adding the table to the dataset, adding columns
to the table etc

HTH,

Bill
 
Thank you Ryan!

There are no problem related to column names. I just can't create/update the
dataset via "Configure dataset with wizard" option.

I can create the dataset manually, but if I tried to configure it via data
source wizard, VS gives me the following information: "The selected dataset
contains objects that can only be viewed with the DataSet Designer. Do you
want to continue with the wizard or edit the dataset in the DataSet Designer?"

Do you know what can it be?

Thank you
Vanessa
 
Yes.

For example, I have a table with just 2 fields:
- code ==> type integer, not null and it is the primary key
- description ==> type char(30)
 
Mysql has this Bug since 2005!!!!!!!!!!!!!!!
It is the shittiest cheapest slowest and most unsecure Database System IMHO.

I am A Software Developer for almost 4 years, and when i remember the big
trouble projects, they were always build on Mysql which caused the trouble...
....
I remember a statement "Delete from table where Text='+textBox1.Text+','"
When executed it deleted everything wchich starts whith textbox1.text.
Any Questions?
AVOID THIS DATABASE!
Use POsgresql, its faster, more secure and it is licensed under Berkley
License and there is no seperation for users in the groups Payer and Leecher.
....So you get the real Deal, not like Mysql!
(e-mail address removed)

url:http://www.ureader.com/msg/14166053.aspx
 
Back
Top