MapInfo Desktop was shipped after MI 4.0 and is compatible with that
version and nothing after.
MapInfo Pro tables are still version 300 and therefore readable by MapInfo
Desktop EXCEPT:
When the table is a linked ODBC table, the version number is 400.
When the table uses MS Access DB's, the version number is 410.
When the table uses 4.5 point sized line widths, the version number is
450.
When the table is a query table, the version number is 450.
When the table uses interleaved line styles, it does not change the
version.
When a table has regions or polylines with node usage greater than the
3.x limit, it keeps it's version but has an 'edit_version' of 450. The
user will be told, when they open this file in a version earlier than
4.5, that they cannot edit this table. The larger objects will not be
displayed and the row will operate as if it did not have an object!
Note that once a table is 'upgraded' to a later version, MI Pro does
not 'downgrade' it to an earlier version if the feature which forced
the 'upgrade' is removed.
Workspaces:
Workspaces appear to be written fresh each time, and so can be
'downgraded' if there are no features that require the 'upgrade'.
MI Pro 4.5 writes 400 at the top of workspaces if they do not contain
any later features
If the user has the label option "Partial Segments" turned on the
version will be at least 410.
If the user uses dot density color or line widths in points the
version will be 450.
Saving queries (controlled by 'Save Queries in Workspaces' check box
in Options>Preferences>Startup dialog) is done as straight Select
statements, does not force a 450 workspace.
Interleaved line styles are encoded in the Pen clause by increasing
the line style value by 128 and does not force a 450 workspace.
MIF/MID:
MIF/MID files created by exporting TAB files from MI Pro match the
version of the TAB file.
We upgrade the MIF version to 450 if the table being exported has date
columns. This is because of the change made to the exported date
format (as of MI Pro 4.5 it is yyyymmdd)
Using the large regions or polylines results in a version 450. There
is no concept of an 'edit_version' in MIF.
Line widths in points are encoded in the Pen clause by multiplying the
line width value by 10 and adding 10 to the result (.2 pts is stored
as a 12, 1.0 pts as 20, etc.). This forces a 450 in the MIF file
header. In MapBasic, you can use these functions: PointsToPenWidth(),
PenWidthToPoints(), and IsPenWidthPixels() instead of having to do the
calculations.
Interleaved line styles is encoded in the Pen clause by increasing the
line style value by 128. This does not force a 450 workspace. In
MapBasic, you can use the PenPattern() function instead of performing
the calculation.
Pen(0,0,0) which was valid previous to 4.5 is not valid in 4.5.
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
