>>After investigating a number of fox (5.0) database problems, we are shocked to discover that it is possible to create a table with a numeric field that has a width of say 5 and decimals of say 3 then store a value of 12345 in this fields. For example:
>>
>>create cursor billy ( numfield n(5,3))
>>insert into billy values 12345
>>
>>Has anybody else looked into this? and can it be a cause of some of the indexing problems that we are currently suffering from? Is this fixed in 6.0?
>
>IMO, this is sensible behavior, and for the best. One must assume the integer portion of a number to be more important than the decimal portion. Thus, it takes precedence in a field with a decimal embedded, and will allow more flexibility this way.

I agree, but it this is not really standard behaviour. If the decimal is to be floating why even make it necessary to declare the decimals when defining the table. I've always assumed the decimals where defined and held in the header of a table so that the decimal/point doesn't have to be stored in the data.