DataTable.Select - Thread.CurrentThread.CurrentCulture - String.Format

I don't know much about DataTable(I've always steered fairly clear of
DataSet), but if this was a regular SqlCommand (etc) I would be adding
a parameter with .Value = aDoubleVar - that way, you don't need to
worry about formatting, plus it is injection safe (think "Bobby
Tables"...).

However, if you /must/ use string concatenation, then you should
ensure that the format is in the known, fixed, expected format of
whatever you are talking to. It is *entirely reasonable* for the user
to use their local (or /locale/) formats and separators, and your code
shouldn't rely on this. This should be used for displaying data to the
user, not exchanging data between systems. You could try passing
CultureInfo.InvariantCulture as the first argument to string.Format
(although you might need a more specific format...).

But I stress; the most reliable option is using parameters.

This is a /similar/ (but unrelated) problem to using the default
encoding / endianness when exchanging text as binary; when talking
between systems it is best to agree in advance what formats to use.

Marc

Hi Marc,

>You could try passing
CultureInfo.InvariantCulture as the first argument to string.Format
(although you might need a more specific format...).

What kind of a Culture is a DataTable using for example on a select? Is it
possible, that it usese the "InvariantCulture" as well?
If that is the case, I could get rid of my problem by following your
suggestion. If not.... :-(

Regards
Rainer

I wouldn't set the culture the invariant - I'd (as indicated) *use*
the invariant culture when I am doing system-to-system calls - i.e.
string.Format(CultureInfo.InvariantCulture, "foo", bar).

Note that there can be issues messing with culture while forms are
displayed; they don't like that much... a simpler option might be to
save the new culture in a settings file, and restart the app? (I
believe that Application has a Restart method or similar).

Also; re supplying proper parameters - I don't really know (not having
done it myself), but is this not the GetFillParameters method on the
data-adapter?

Marc

Hi Mark,

"Marc Gravell" <ma**********@gmail.comschrieb im Newsbeitrag
news:3b**********************************@k39g2000 hsf.googlegroups.com...

>I wouldn't set the culture the invariant - I'd (as indicated) *use*
the invariant culture when I am doing system-to-system calls - i.e.
string.Format(CultureInfo.InvariantCulture, "foo", bar).

Yes, that is what I am currently doing (ref my other answer/question).

Note that there can be issues messing with culture while forms are
displayed; they don't like that much... a simpler option might be to
save the new culture in a settings file, and restart the app? (I
believe that Application has a Restart method or similar).

It surely would be better, to set the culture and the stop/restart the
application. Unfortunately it is a request from my customer, that the app
must be able to switch rultures at runtime. Acutally this is working quite
good. I used the method pointed out in
http://dzaebel.net/LocalizeRuntime.htm by Frank Dzaeble.

Also; re supplying proper parameters - I don't really know (not having
done it myself), but is this not the GetFillParameters method on the
data-adapter?

You are right, but I dont have a data-adapter, since I am working with a
"standalone" typed DataSet.

As mentioned above, I am already following your suggestion, and am using
CultureInfo.InvariantCulture to do my String.Format on selectStr generation.
It seems to be working fine, which leads me to the thought, that DataSets
are using CultureInfo.InvariantCulture internaly as well.
If someone could state this true, I can replace "seems to" with "is" ;-)

Regards
Rainer