You can now create Native and NativeX tables supporting each node's Z and M values. MapBasic support for creating Native and NativeX tables with M/Z supportmz token is added.
For example,
Create Map For Untitled CoordSys Earth Projection 1, 104 supportmzThe new token SupportMZ{On|Off}] in the Commit Table
statement indicates if the destination table contains M and/or Z values. This is an
optional parameter. If not passed, the table is saved with M,Z values from the source
table.
Commit Table table
[ As filespec
[ Type { NATIVE [ Charset char_set ] |
NATIVEX [ Charset char_set ] [ Locale locale ] |
DBF [ Charset char_set ] |
Access Database database_filespec Version version Table tablename
[ Password pwd ] [ Charset char_set ] |
QUERY |
ODBC Connection ConnectionNumber Table tablename
[ Type SQLServerSpatial { Geometry | Geography } ]
[ ConvertDateTime { ON | OFF | INTERACTIVE } ] |
GPKG [ Database database_filespec ] [ Table tablename ]
[ Charset char_set ] } ]
[ CoordSys... ]
[ Version version_pro ] ]
[ Interactive ]
[ SupportMZ {On|Off} ]
[ Background [View None|Automatic|Map|Browse|Add To Map]
[Into { Variable var_name }] [Calling mb_sub_with_1_param_and_error_trap] ]
[ BlockSize block_size ]
[ { Interactive | Automatic commit_keyword } ]
[ ConvertObjects { ON | OFF | INTERACTIVE } ]