Hi Hilmar and Fabio.
I would, in a way, support Fabio in terms of bringing MS SQL SERVERness into VFP data types (field and variables). I, contrary to Fabio, deal with big numbers. To do maths on 15+ digit numbers you have to construct complex and poorly tested (we are talking big time money here) kludges.

Best wishes.
Kamil


>For me, this hasn't caused a major problem. I seldom need this level of precision.
>
>If it is a problem for you, you may want to switch to a strongly typed language (for instance, Delphi), which allows you - nay, forces you - to control the type of each and every variable. I think you will also have a wider variety of data types in some languages (I am not sure exactly what you get in Delphi): types like 1, 2, 4 or 8-bit integers, BCD, floating-point that has a somewhat greater precision (more significant digits) than what is available in VFP.
>
>>Hilmar,
>>
>>Me it seems of living in an other planet.
>>
>>On SQL Server, Oracle ... the schema for
>>- data type,
>>- precision of data,
>>- precision of result,
>>- implicit conversion of numeric
>>- the literal numerical values
>>
>>he is rigorous and coherent.
>>
>>On VFP every calculation has one its history,
>>if use the fields I have a result
>>if use the variable ones of it I have an other
>>if use eval() I can have of an other
>>if use the macro I can have an other
>>...
>>
>>To me it seems a madness,
>>perhaps but it has been a madness the day that I have chosen VFP like development enviroment.
>>
>>Fabio