File versions and tab, mif/mid, and wor support – Pitney Bowes MapInfo Professional User Manual
Page 488
File Versions and TAB, MIF/MID, and WOR Support
The following table lists changes (and their implications) to versions in .tab, workspace, and other files
used by MapInfo Professional.
• TAB files are always saved as 300 unless noted in the table
• WOR files are always saved as 400 unless noted in the table
• Once a table is 'upgraded' to a later version, MapInfo Professional does not 'downgrade' it to an earlier
version if the feature which forced the 'upgrade' is removed.
• Workspaces are written fresh each time, and Workspace versions can be decreased if there are no
features in them that require using a higher version.
• Pen(0,0,0) and Brush(0,0,0), which were valid in MapInfo Professional 4.1 tables are not valid in
MapInfo Professional 4.5 and later.
• Line widths in points is encoded in the Pen clause by multiplying the line width value by 10 and
adding 10 to the result (.2 -> 12, 1.0 -> 20, etc.). This forces a 450 in the MIF file header.
• Interleaved line styles are encoded in the Pen clause by increasing the line style value by 128. This
does not force a 450 workspace, it is 4.x compatible, and is saved as 400 TAB.
Version 4.0.0 (400)
:
Action
WOR
MIF-MID
TAB
Table is a linked ODBC table.
X
Tab version stays at 300 with interleaved.
X
X
X
Saved queries are implemented as straight Select
statements. (Saved queries are controlled by the
X
Save Queries in Workspaces check box on the
Options menu, point to Preferences and click
Startup.)
Version 4.1.0 (410)
:
Action
WOR
MIF-MID
TAB
Table uses MS Access DB's.
X
X
Version 4.5.0 (450)
:
Action
WOR
MIF-MID
TAB
Region and polyline objects, that have more than
32K nodes (actually !edit_version 450 and !version
300).
X
X
Table uses point sized line widths.
X
X
Table is a query table.
X
X
MapInfo Professional 12.5
488
File Versions and TAB, MIF/MID, and WOR Support