For example's sake, I have a field called Price which is N(10,6).

If I enter a value of at least 1000, VFP will store this value and move the decimal point over to the right to accommodate the larger number (i.e. increased digits to the left of the decimal point).

My recollection of earlier VFP versions is that the attempt of storing a larger number as described above would result in a numeric overflow, which is exactly what I would expect. It seems to me that the newest version is not truly honoring the structure definition at all. Is there now a new VFP setting that needs to be configured to go back to this old behavior?

The reason this is a problem is because our structure was specifically guarding against numbers that are too large that wouldn't make sense. One of our clients has a downstream process that explodes because their own structure in SQL Server was set to match ours. Subsequently, a large erroneous number got stored and is killing their DTS process.

Any ideas?