Re: Truncated Data

[Fred]

You are on the right path here. The Migration Tool Kit converted MS SQL fields
defined as Float - 8 bytes to Double(53,30) where 53 is the number of significant
digits and 30 is the number of decimal places. While this may be correct from a syntax
standpoint, it is looks to me like the data field is too large for the system to handle.
Maybe the data is there but neither Navicat nor MS Access linked tables can read it
and you cannot get the fields to accept a value larger than "10".

Is there a global way to control how this data is defined during the reverse engineering
process to force smaller data ranges?

I have been able to force different outcomes by using the capability to set the
characteristics of individual columns during the mapping process but it is just guess
work as there is no documentation. I can force a field to be a FLOAT(12,4) with the
following:

autoDecimalDigits=no, forceDatatypeName=FLOAT, forceDecimalDigits=yes,
forceLength=yes, forceLengthValue=4, forcePrecisionValue=12, forceScaleValue=4.
You must do this in every table at the column level - quite tedious.

I suspect if this is what needs to be done I would force a DOUBLE(12,4) instead
because of the problems in MySQL with Floating Point comparisons.

Thanks for you help.