A SQL NUMERIC datatype of (7,3) stores .3 as .299, .6 as .599, and .7 as .699. The table being used is a VFP remote view, and the problem occurs when an update to SQL is issued. If an integer is in the value, this does not happen in most instances, though it does occur with 1.9, changing it to 1.899. The numbers .3, .6, and .7 are stored with approximation in a FLOAT datatype because they cannot be accurately represented in binary notation. Does this mean this a problem with these numbers with the NUMERIC datatype as well?