thousands separator in numeric fields via ODBC

Hello,
when I select data>=1000 from foxpro numeric fields with decimal places
I start receiving a comma as a thousands separator. I've looked through the
ODBC help but I'm still not sure why this is happening, any ideas? I'd like
to have no separator.

--
TIA
Andrew Howell

Fred
Wed Feb 04 09:03:16 CST 2004

It's not a numeric value if it has punctation other than sign or decimal
point. A number does not know from separators, that's a formatting in text
only thing.

Fred
Microsoft Visual FoxPro MVP


"Andrew Howell" <ajh@work> wrote in message
news:OhdsXmy6DHA.1368@TK2MSFTNGP10.phx.gbl...
> Hello,
> when I select data>=1000 from foxpro numeric fields with decimal
places
> I start receiving a comma as a thousands separator. I've looked through
the
> ODBC help but I'm still not sure why this is happening, any ideas? I'd
like
> to have no separator.
>
> --
> TIA
> Andrew Howell
>
>

Andrew
Wed Feb 04 10:04:23 CST 2004

"Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
news:<#soKNBz6DHA.3648@TK2MSFTNGP11.phx.gbl>...
> It's not a numeric value if it has punctation other than sign or decimal
> point. A number does not know from separators, that's a formatting in
text
> only thing.

I hear what you are saying but for whatever reason, every type of data in my
fox tables is being returned as character data except logical fields when I
query with ODBC.

With numeric fields, thousands separators are also being added if there are
decimal places in the numeric fields [ie N(10,x) where x>0] but I can see
nothing that controls this in the ODBC settings.

The ODBC driver is v6.01.8629.01 and the fox tables are FPW2.6a tables.

--
Best regards
Andrew Howell

Fred
Sat Feb 07 15:34:03 CST 2004

I'm sorry, I've tried that with everything I can image. That version of the
driver sure seems to return the correct field types and sizes for me. Have
you tried it using a SQLSTRINGCONNECT() instead of a DSN?

Fred
Microsoft Visual FoxPro MVP

"Andrew Howell" <ajh@work> wrote in message
news:uYn5Piz6DHA.2644@TK2MSFTNGP11.phx.gbl...
> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
> news:<#soKNBz6DHA.3648@TK2MSFTNGP11.phx.gbl>...
> > It's not a numeric value if it has punctation other than sign or decimal
> > point. A number does not know from separators, that's a formatting in
> text
> > only thing.
>
> I hear what you are saying but for whatever reason, every type of data in
my
> fox tables is being returned as character data except logical fields when
I
> query with ODBC.
>
> With numeric fields, thousands separators are also being added if there
are
> decimal places in the numeric fields [ie N(10,x) where x>0] but I can see
> nothing that controls this in the ODBC settings.
>
> The ODBC driver is v6.01.8629.01 and the fox tables are FPW2.6a tables.
>
> --
> Best regards
> Andrew Howell
>
>

Andrew
Mon Feb 09 02:32:42 CST 2004

Fred Taylor wrote:
> I'm sorry, I've tried that with everything I can image. That version
> of the driver sure seems to return the correct field types and sizes
> for me. Have you tried it using a SQLSTRINGCONNECT() instead of a
> DSN?

Thanks for persevering Fred, I'm working with PHP and after your first post
[and my second..] I tried looking on the PHP side of things. The answer I've
received this morning is that the PHP extension is requesting the ODBC
driver to convert the numerics to strings because there isn't a numeric type
in PHP.
Not to worry, now I know this I shall handle it in PHP.

Thanks again
Andrwe Howell

Fred
Mon Feb 09 09:13:43 CST 2004

Well, that makes it a little hard to get there from here, then. <g>
Thanks for letting me know where the problem is.

Fred
Microsoft Visual FoxPro MVP

"Andrew Howell" <ajh@work> wrote in message
news:O8jYshu7DHA.2064@TK2MSFTNGP11.phx.gbl...
> Fred Taylor wrote:
> > I'm sorry, I've tried that with everything I can image. That version
> > of the driver sure seems to return the correct field types and sizes
> > for me. Have you tried it using a SQLSTRINGCONNECT() instead of a
> > DSN?
>
> Thanks for persevering Fred, I'm working with PHP and after your first
post
> [and my second..] I tried looking on the PHP side of things. The answer
I've
> received this morning is that the PHP extension is requesting the ODBC
> driver to convert the numerics to strings because there isn't a numeric
type
> in PHP.
> Not to worry, now I know this I shall handle it in PHP.
>
> Thanks again
> Andrwe Howell
>
>