I am having a problem and I want to know if anyone else has encountered this problem,
contacted MapInfo about, and/or determined a work-around or solution for it.
We have tables containing approx 1.5 million records contain in Oracle databases.
Previously we were using Oracle version 9.0.1 and we recently upgraded to version
9.2.0.4. We have been using MapInfo version 7.0 for the whole time.
A unique ID field is created called "MI_PRINX" when a table is loaded/imported into
Oracle. This field has always been type FLOAT in MapInfo. When extracting data from
the Oracle 9.0.1 database thru MapInfo 7.0's "oracle spatial" capabilities it shows up
as float.
However, when fetching data from Oracle 9.2.0.4 using the same MapInfo 7.0's "oracle
spatial" capability, the MI_PRINX field AND ALL OTHER type FLOAT fields are being
designated by MapInfo 7.0 as type Decimal (2,0) which causes any number in that field
of 100 or greater to be converted to the number 99.
We have checked using Oracle software to determine that the data in tables in the
Oracle Database are still correct and showing the correct values. It is only when
fetching data from the tables using MapInfo 7.0 that the data becomes "corrupted"
because MapInfo insists on viewing these fields as Decimal (2,0) instead of FLOAT.
This happens both on tables loaded thru MapInfo's EasyLoader AND thru tables exported
from our Oracle 9.0.1 database and then imported into the 9.2.0.4 database. (Yes, we
still have a copy of our older 9.0.1 database and the process continues to work
correctly there).
Anything helpful would be appreciated. (I am also sending this to MapInfo tech
support, btw).
Also wondering if this problem still occurs in MI-7.5
-Evan MacDougall
GIS Supervisor - DPSI
[EMAIL PROTECTED]
(800)736-3109/(310)342-3600 - ext. 3681
