Pitney Bowes MapInfo Professional - Manual (Page 197)

1. Open a remote DBMS connection and select a live table for display.
2. From the Map menu, click Create Legend to display the Create Legend - Choose Layers dialog
box.
3. Select a layer to create a legend from and click Next to display the Create Legend - Legend Default
Properties dialog box.
4. Click Next to display the Create Legend - Frame Properties dialog box.
5. In the Styles from box, there are three options. The first option, map catalog, provides the existing
support and is still the default for live tables.
• Select map catalog to retrieve the default styles for the selected legend frame from the map
catalog. Use this option when you are concerned with performance. Retrieving map styles from
live tables on a remote database can take a long time, but retrieving a default style from the map
catalog can be significantly faster. Remember that styles in the map catalog may not be as visually
descriptive as the other options. This is the default option for live tables, but is disabled for other
types of tables.
• Select unique map styles to retrieve all unique object styles for the live access table for a visually
appealing legend. For extremely large tables, this option can take longer than the first option. This
option is selected by default when the legend frame is not a live access table.
• Select unique values in a column to retrieve the styles associated with the values saved in a
particular column in the database table for a visually appealing legend. For extremely large tables,
this option can take longer than the first option.
6. Click Save frame setting to Metadata to preserve the choice you made in this dialog box. When
you re-open this dialog box the settings from the metadata are used as default values instead of the
system set default values.
7. Click Finish.
See Troubleshooting DBMS Table Issues in the Help System.
MapInfo Professional does not Maintain the Curve Type in Oracle Data
When reading Oracle tables, MapInfo Professional changes records containing geometries that do not
directly translate to MapInfo Professional geometry types. This happens when working with lines and
polygon boundaries containing segments that are curve types or circles. MapInfo Professional does not
support the curve type, so it converts these to polylines. MapInfo Professional also converts circles into
regions. When saving these records back to the database, you may lose some topological information
as a result. This is something to be aware of when sharing your Oracle data with other applications, such
as Autodesk's Map3D.
MapInfo Professional shows a message before saving data back to the Oracle database when that data
contains curved geometries. The message is as follows:
The Oracle table you are updating contains one or more geometry types that MapInfo Professional does
not support, so the geometry type has been converted to a supported type. Saving these geometries
may introduce topological errors into your database. Click Yes to continue, or No to discard changes
that were made to unsupported geometries. Edits to attribute data save in either case.
When executing the MapBasic Commit statement, the prompt displays only when it contains the
Interactive keyword. Note:
Converting Unsupported Geometries in Oracle
Some times when you are creating a Map in MapInfo Professional and you are storing the results in
Oracle you create maps which use geometries that are not supported: Oracle does not support arcs,
ellipses, rectangles, and rounded rectangles.
If you have created a map you do not want to lose but cannot save to the DBMS of your choice
due to unsupported geometries, then use the Save As menu option and save the map without
the unsupported geometries. Note:
Oracle Geometry Conversion Behavior
197 MapInfo Professional User Guide
Chapter 7: Working with Data in a DBMS