Considerations when Working with Linked Tables - MapInfo_Pro - 2023

MapInfo Pro Help

Product type
Software
Portfolio
Locate
Product family
MapInfo
Product
MapInfo > MapInfo Pro
Version
2023
Language
English
Product name
MapInfo Pro
Title
MapInfo Pro Help
First publish date
1985
Last updated
2023-09-12
Published on
2023-09-12T16:39:16.995549

The following conditions must be met to edit a linked table:

  • You must select from a single table.
  • You must have update access to the table.

    Some fields in a table may be read-only. In mappable linked tables, you can edit the objects

  • The table must have a unique index or a primary key constraint defined.

    These are the primary key or unique index columns. They enable updates to be reliably committed to the server table. If you insert a new row or edit an existing row, the value in these fields must be unique within the ODBC Database table or you will receive an error during the commit.

  • You must include at least one editable field in the column selection list.

    Extra fields may be included in the linked table for updates.

A field in an ODBC Linked table is not editable when:

  • It is a read-only column in the result set (as indicated by the ODBC Data Source).
  • It is a long character data type in the ODBC Database (width > 254).
  • It is a BINARY data type in the ODBC Database (returned as a string of Hexadecimal characters).
  • It is a TIME data type in the ODBC Database (returned as a MapInfo Date, displayed as blank).

If the total number of rows stored in the MapInfo_MapCatalog is out of sync with the actual number of rows in the table, some things may not work correctly. The map will always include all of the map objects, but the following could occur:

  • The row count displayed in the Browser is incorrect.
  • The MapBasic statement to fetch last does not return the correct row.
  • Thematic maps, particularly ranged thematic maps, may be wrong.