This is useful to know Peter. Changing tack slightly but on the subject of backwards compatibility, I had saved some layout workspaces in v17 which wouldn't open for users in v15 - this was because the printer was set to MapInfo v17 PDF printer:
Set Window FrontWindow() Printer
Name "MapInfo PDF Printer Version 17.0 x64" Orientation Landscape Copies 1
I've fixed it but something we need to be aware of.
------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK
------------------------------
Original Message:
Sent: 01-22-2020 03:03
From: Peter Horsbøll Møller
Subject: Version 2019 format over v17
Hi John
There is no change to the tab file format between v17 and v2019.
You'll, however, find that these features will create a v2019 workspace if you use any of them:
- Notifications window state saved in WOR
- Query Builder window state saved in WOR
- If a saved query has Limit clause
- Using new SQL syntax for column alias, table alias, aggregate spatial functions, cross join, table.* or object map
You can always find an overview of the file format changes in the Help System. Look for File Versions and TAB, MIF/MID, and WOR Support.
------------------------------
Peter Horsbøll Møller
Distinguished Engineer
Pitney Bowes Software & Data
Original Message:
Sent: 01-21-2020 11:53
From: John Ievers
Subject: Version 2019 format over v17
Hello
Wondering if there are any new features in v2019 that would stamp in the tab file different from v17
i.e. can v17 users happily mingle with v19 users without worry?
------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------