By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,723 Members | 850 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,723 IT Pros & Developers. It's quick & easy.

DataSet Locale problem

P: n/a
I have an application that utilizes a dataset. I've found just today, that
if the regional language settings are changed at the point of where I
instantiate the DataSet an error is thrown of: "Cannot add a DataRelation or
Constraint that has different Locale or CaseSensitive settings between its
parent and child tables." The particular dataset in question contains 4
tables. All state that the locale is "English (United States)"

A few things of interest:
1: In three of the four tables the Locale is listed in the properties
bolded, as if it's a default that's been changed. The fourth is in standard
font.
2: Attempting to change any of the locale settings results in a "Propety Is
Not Valid" dialog with details that state: "Cannot change CaseSensitive or
Locale property. This change would lead to at least one DataRelation or
Constraint to have different Locale or CaseSensitive settings between its
related tables."
3: CaseSenstive for all four tables is False
4: If I change the regional settings on my development machine to "Dutch
(Netherlands)" and attempt to load the DataSet in the VS dataset designer,
it won't allow me, stating the same error as when I try to instantiate at
runtime.
5: This is what I think may be the key: The first three tables were added by
dragging from server explorer from an MSDE instance. Then I migrated the
application to SQLExpress and added another table. This table was added by
dragging from the SQL Express instance to the dataset designer. The three
tables that list the Locale property in bold are the tables that were added
from the MSDE instance. The fourth is from the SQLExpress instance.

I have tried removing each of the tables from the dataset and re-adding them
and re-creating the relations, but that doesn't seem to make any difference.

This really has me stumped. Any suggestions?
Feb 8 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I've solved this problem, and wanted to post back the answer.

The fourth table that was causing the problems had a TableAdapter attached
to it that could be seen in the dataset designer. As this isn't used
anywhere in my code, I simply removed it and all is working fine.

"Matt F" <mf****************@nospam.nospamwrote in message
news:OO**************@TK2MSFTNGP04.phx.gbl...
>I have an application that utilizes a dataset. I've found just today, that
if the regional language settings are changed at the point of where I
instantiate the DataSet an error is thrown of: "Cannot add a DataRelation
or Constraint that has different Locale or CaseSensitive settings between
its parent and child tables." The particular dataset in question contains
4 tables. All state that the locale is "English (United States)"

A few things of interest:
1: In three of the four tables the Locale is listed in the properties
bolded, as if it's a default that's been changed. The fourth is in
standard font.
2: Attempting to change any of the locale settings results in a "Propety
Is Not Valid" dialog with details that state: "Cannot change CaseSensitive
or Locale property. This change would lead to at least one DataRelation or
Constraint to have different Locale or CaseSensitive settings between its
related tables."
3: CaseSenstive for all four tables is False
4: If I change the regional settings on my development machine to "Dutch
(Netherlands)" and attempt to load the DataSet in the VS dataset designer,
it won't allow me, stating the same error as when I try to instantiate at
runtime.
5: This is what I think may be the key: The first three tables were added
by dragging from server explorer from an MSDE instance. Then I migrated
the application to SQLExpress and added another table. This table was
added by dragging from the SQL Express instance to the dataset designer.
The three tables that list the Locale property in bold are the tables that
were added from the MSDE instance. The fourth is from the SQLExpress
instance.

I have tried removing each of the tables from the dataset and re-adding
them and re-creating the relations, but that doesn't seem to make any
difference.

This really has me stumped. Any suggestions?


Feb 8 '07 #2

P: n/a
Thanks Matt,

I was curious what this could be.

Cor

"Matt F" <mf****************@nospam.nospamschreef in bericht
news:O3**************@TK2MSFTNGP03.phx.gbl...
I've solved this problem, and wanted to post back the answer.

The fourth table that was causing the problems had a TableAdapter attached
to it that could be seen in the dataset designer. As this isn't used
anywhere in my code, I simply removed it and all is working fine.

"Matt F" <mf****************@nospam.nospamwrote in message
news:OO**************@TK2MSFTNGP04.phx.gbl...
>>I have an application that utilizes a dataset. I've found just today,
that if the regional language settings are changed at the point of where I
instantiate the DataSet an error is thrown of: "Cannot add a DataRelation
or Constraint that has different Locale or CaseSensitive settings between
its parent and child tables." The particular dataset in question contains
4 tables. All state that the locale is "English (United States)"

A few things of interest:
1: In three of the four tables the Locale is listed in the properties
bolded, as if it's a default that's been changed. The fourth is in
standard font.
2: Attempting to change any of the locale settings results in a "Propety
Is Not Valid" dialog with details that state: "Cannot change
CaseSensitive or Locale property. This change would lead to at least one
DataRelation or Constraint to have different Locale or CaseSensitive
settings between its related tables."
3: CaseSenstive for all four tables is False
4: If I change the regional settings on my development machine to "Dutch
(Netherlands)" and attempt to load the DataSet in the VS dataset
designer, it won't allow me, stating the same error as when I try to
instantiate at runtime.
5: This is what I think may be the key: The first three tables were added
by dragging from server explorer from an MSDE instance. Then I migrated
the application to SQLExpress and added another table. This table was
added by dragging from the SQL Express instance to the dataset designer.
The three tables that list the Locale property in bold are the tables
that were added from the MSDE instance. The fourth is from the
SQLExpress instance.

I have tried removing each of the tables from the dataset and re-adding
them and re-creating the relations, but that doesn't seem to make any
difference.

This really has me stumped. Any suggestions?



Feb 8 '07 #3

P: n/a
Hi Matt,

We need to perform more research on this issue . We will reply here as soon
as possible.
If you have any more concerns on it, please feel free to post here.

Thanks for your understanding!
Best regards,
Wen Yuan

Feb 8 '07 #4

P: n/a
Thanks Matt,

It seems like I posted too fast. I'm very glad to hear you have resolve the
issue and kindly post back the solution. Thank for your information, again.

Have a great day!
Best regards,
Wen Yuan

Feb 8 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.