Subject | Localisation |
---|---|
Author | Robert martin |
Post date | 2011-03-07T02:22:56Z |
Hi
Doing a spot of localisation in our app. In Europe a , is used as a
decimal separator. I have noticed that FB / IBO ignores this and the .
is used even when your computer is setup otherwise (i.e. Italy). Is
this always correct, will FB / IBO always expect . in SQL strings?
I have been changing our app to not build SQL strings where a Float is
to be built into the string. I use parameters instead. However I have
hit a couple of places where this is not possible (in one case building
an EditSQL SQL in a TIBOQuery). Is it safe to just convert the float
into nnnn.nn ?
Not sure if I should as the FB list but thought I would try here first
in case the . functionality is IBO specific.
Thanks
Rob
Doing a spot of localisation in our app. In Europe a , is used as a
decimal separator. I have noticed that FB / IBO ignores this and the .
is used even when your computer is setup otherwise (i.e. Italy). Is
this always correct, will FB / IBO always expect . in SQL strings?
I have been changing our app to not build SQL strings where a Float is
to be built into the string. I use parameters instead. However I have
hit a couple of places where this is not possible (in one case building
an EditSQL SQL in a TIBOQuery). Is it safe to just convert the float
into nnnn.nn ?
Not sure if I should as the FB list but thought I would try here first
in case the . functionality is IBO specific.
Thanks
Rob