VERIFIED SOLUTION i
What are the new limits and behaviors for MapInfo Professional Tables and other supported file types?
***Dated August 2014***
New BehaviorThe new byte limit is now increased to 65,534. Due to other limits, it is actually impossible to hit this limit when creating a table in MapInfo Professional. We have a limit of 250 columns and a limit of 254 characters in a column. Therefore, the longest record which can be created at present is 63,500 bytes (250 x 254).
Table VersionsSince older versions of MapInfo would either crash or behave oddly when attempting to open tables with record lengths exceeding the old 4000-byte limit, tables which exceed the old limit will have a version number of 1200. Older versions of MapInfo will not be permitted to open such tables.
Saving to and Re-opening Other Formats
DBFThere appear to be no issues saving as DBF and re-opening the table. When we save the table it will be version 1200, so older version of MapInfo will not be able to open it. In addition, both Excel and an application called DBF Viewer 2000 can both open the resulting DBF file.
MS AccessMS Access can create tables whose defined record length is large, but there is an actual byte limit for a single record of only 2,000 bytes. We will error if trying to save records with more data in a record. This is true even in the current version of MapInfo. Note that the byte limit appears to be an actual limit of MS Access and not simply a problem with our MS Access implementation.
SQLiteAt present we have been unable to save to SQLite.
RDBLarge record length tables can be saved to RDB tables. We will not force the version to 1200. As noted above, older versions of MapInfo will be able to open the table but will not be able to edit or cache the table.
Exporting to and Importing from Other Formats
MIFThere appear to be no issues exporting to MIF and re-importing. The tables created when importing should be version 1200.
DBFThere appear to be no issues exporting to DBF and opening the DBF as a table. When we open the DBF as a table, the table version should be 1200. In addition, both Excel and an application called DBF Viewer 2000 can both open the resulting DBF file.
Delimited ASCII/CSVThere appear to be no issues exporting to ASCII/CSV. We do not check or enforce a record length when opening an ASCII/CSV file as a table, so the table version is not forced to be 1200. Older versions of MapInfo will be able to open the table, but the old byte limit for ASCII/CSV tables was 4,096 bytes. So even though we open tables with longer record lengths in older versions without error, the data is truncated.
DXFThere appear to be no issues exporting to DXF and re-importing. The tables created when importing should be version 1200.
Opening Other Formats
ExcelThere is no explicit record limit for Excel tables. Tables with large record lengths can be already be opened in the current version of MapInfo. Since Excel tables are read-only in MapInfo, the issue with transaction files does not apply.
Linked RDBLinked RDB tables use a Native table to store the local copy. We can open RDB tables as linked tables with record lengths up to the new limit. Such tables should be version 1200.
WFSSince WFS tables are similar to liked tables, we should be able to open tables with large record lengths. Such tables should be version 1200. However, this has not yet been tested.
Shape fileSafe has a new version of MFAL/TranslatorAPI and they should have already incorporated this into the new Universal Translator. The UT enforces a 32,768 byte limit for a Shapefile however. It is not clear if this is the actual limit for a Shapefile.
MFALA test has been written which creates, writes to, reopens, and reads a table with a large record length.
EasyLoaderWe do not yet have a version of EasyLoader with the new version of MFAL which supports large record length. Until we do, we cannot tell if there will be any issues until the implementation and testing will has been completed.
UT/Open Universal DataWe have provided Safe with a new build of Mfal\trnapi
Other FeaturesOther features except where noted below should work as before. For example, cut/copy/paste should work with larger record lengths.
Crystal ReportsCrystal Reports creates and uses a MS Access table. As noted above MS Access tables have a record byte limit of 2,000. This will be an issue for large record length tables, but it was already an issue for tables that exceed that limit.
A file is attached that can be provided to customers.
UPDATED: April 10, 2017