>>XBase tables store all their data (with certain exceptions in memo and
>>general fields) as ASCII characters. This means that at some point in the
>>process this data has to be translated from character to 8 byte double
>>precision floating point numbers for your numeric fields. By contrast,
>the
>>C program may not have this overhead.
>
>
>this is no longer true in VFP
>integer,double and datetime are binary type
>(this is one of the reasons integer is the prefered "primary index" )
>integer - 4 byte
>double 8 byte (this is not like Float which is just like numeric)
>
>
>Arnon

Arnon,

Ya got me! But if Peter's using numeric rather than say floats for his floating point numbers, for example, then it still does apply even in VFP 3.0 type tables. In those, type numeric is still stored as character. What it ends up being converted to is problematic at best.

It's also a good point to remembver for anyone converting a 2.x system to VFP. Coversion needs to be done down to the table structure level, and not just the programming and DBC point.

George