
Signature
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
Darrell sent me his data offline. His connection string and code were fine -
I could open other tables with them, but his data appears to be corrupt.
Evidently the Fox ODBC drivers are a little more forgiving than the OLE DB
data provider.
I played with the data and was able to read his table when it had only one
record and a value of 1/"1" in each field. I was also able to read the data
when all the Numeric fields were changed to character (Fox stores Numeric
fields internally in character format), or Currency (not stored as
characters).
It appears that this particular data will need to be read via ODBC, unless
the offending item can be found.

Signature
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
> Hi Darrell,
>
[quoted text clipped - 37 lines]
>>>
>>> -ralph
Darrell Wesley - 29 Aug 2005 17:01 GMT
Cindy,
I found 2 fields that the data in them didn't match the field specifications
exactly.
DISPLACE was defined as Numeric 5 wide with 2 decimals the data it
contained was like 132.6 which matched the field widt but not the decimals.
Typing values into this field interactively in a browse table showed that the
maximum value you could enter was 99.99 if you attempted to enter 132.6 it
would turn out to be 13.62.
TOTWGT was defined as 6 wide with 1 decimal and had a value like 12733. ,
the maximum value I could enter was 9999.9.
It looks like FoxPro itself doesn't care about this and will use the
embedded decimal point similar to Fortran but other programs that use the
latest OLEDB drivers need to have data that matches the field specs exactly.
You might want to feed this back to the FoxPro team as a possible "BUG".
> Darrell sent me his data offline. His connection string and code were fine -
> I could open other tables with them, but his data appears to be corrupt.
[quoted text clipped - 51 lines]
> >>>
> >>> -ralph
Cindy Winegarden - 29 Aug 2005 22:06 GMT
Hi Darrell,
It's interesting to know what you found. You could adjust the table
structure to accommodate those out-of-range values.
I'll pass your comments along to my contacts at Microsoft.

Signature
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
> Cindy,
>
[quoted text clipped - 85 lines]
>> >>>
>> >>> -ralph