Re: Data Definition for Numeric data type

Tech-Archive recommends: Speed Up your PC by fixing your registry

On Nov 26, 12:11 pm, "Ralph" <nt_consultin...@xxxxxxxxx> wrote:
"DK" <dwes...@xxxxxxxxxxxxx> wrote in message

news:0d81e1ae-b809-4bfd-8299-cc9ddae70c60@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx





On Nov 22, 6:24 pm, "Ralph" <nt_consultin...@xxxxxxxxx> wrote:
"DK" <dwes...@xxxxxxxxxxxxx> wrote in message

<snipped>

It's VB6 and historically if the the data in the field does not match
exactly the field spec you will either get some strang EFail staus
that tells yo nothing or get no data returned in the record set.

The code is very simple "Select * from Table", if any of the rows that
would have been returned has this field no data will be returned in
the recordset but if you include all but the offending field data will
be returned.

Usually this is used to build a grid with all of the available records
in it (it does have a where clause and a limited set of fields) and
then you can select one of the rows and retrieve the balance of the
data. BUT if the row you selected has the offending field then you get
no records returned in other words you get an immediate EOF.

It makes no difference which of the various OLEDB drivers for FoxPro
gets used. I have found by experimentation that the older ODBC driver
will return data.

That is strange. I've never had any particular problem of that sort with the
Numeric datatype. Without something I can reproduce I not going to be much
help.

The FoxPro guru around here is Cindy. Hopefully she will show up and help.
[Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegar...@xxxxxxx www.cindywinegarden.com]

-ralph- Hide quoted text -

- Show quoted text -

Ralph,
I think Cindy has looked at this problem in the past just thought
there may be something new out there.
.