MapInfo Pro

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Hi John
I don't think Pro ever downgrades the version once it has been stamped into the tab file header.

You have two options:
1. Export your table to MIF/MID and import MIF/MID back into a table. This will reset the table version in the tab file header
2. Make sure the table doesn't hold features that require a higher table version. If that's not the case, manually change the table version.

------------------------------
Peter Horsbøll Møller
Pitney Bowes
------------------------------

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Hi Peter
In my tests with v17.0.3; if you save an extended tab to classic tab then it is stamped as v15.2 and therefore requires 64-bit MapInfo.
If you save the same selection initially to a classic tab then it is stamped as v4.5
A bit of a pitfall - depends on the circumstances.
(or just edit the tab header to v450 !!)

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Original Message:
Sent: 06-24-2019 15:53
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

Hi John
I don't think Pro ever downgrades the version once it has been stamped into the tab file header.

You have two options:
1. Export your table to MIF/MID and import MIF/MID back into a table. This will reset the table version in the tab file header
2. Make sure the table doesn't hold features that require a higher table version. If that's not the case, manually change the table version.

------------------------------
Peter Horsbøll Møller
Pitney Bowes

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew
------------------------------

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well. 

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY
------------------------------

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Another guaranteed safe way to get the correct version is to create a new table and then append rows. It's a bit more steps but it guaranteed to be correct. 450 may not be right.

To do this:
1) create a new table from the old table (same structure), pick the right format and save the table.
2) Then append all the rows from the original to the new.  This will make all the records go through our transaction code which decides on the version based on the data.
3) You then do have to save the table as the appends are edits. 
The reason Save Table as does not do the versioning correctly is that it does not create transactions.  The table is written and not even open.
Perhaps a feature request could allow this to happen automatically. However, if you wanted the saved copy to have the same name as the original in a different folder, other changes would have to occur. 
​

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY
------------------------------

Original Message:
Sent: 06-25-2019 15:14
From: Andrei Veselov
Subject: Save As Native Tab stamps it as v15.2

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well.

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Tech Support has created an article that ​describes Eric's workaround for versioning the data that you may find helpful.

------------------------------
[Dave] [Sepowski]
[Support Analyst]
[Pitney Bowes]
[Troy] [NY]
------------------------------

Original Message:
Sent: 07-01-2019 16:46
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Another guaranteed safe way to get the correct version is to create a new table and then append rows. It's a bit more steps but it guaranteed to be correct. 450 may not be right.

To do this:
1) create a new table from the old table (same structure), pick the right format and save the table.
2) Then append all the rows from the original to the new.  This will make all the records go through our transaction code which decides on the version based on the data.
3) You then do have to save the table as the appends are edits.
The reason Save Table as does not do the versioning correctly is that it does not create transactions.  The table is written and not even open.
Perhaps a feature request could allow this to happen automatically. However, if you wanted the saved copy to have the same name as the original in a different folder, other changes would have to occur.
​

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 06-25-2019 15:14
From: Andrei Veselov
Subject: Save As Native Tab stamps it as v15.2

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well.

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Thanks Eric
That makes sense.
Would a Select All > Copy > Paste into the new table have the same effect?


------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Original Message:
Sent: 07-01-2019 16:46
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Another guaranteed safe way to get the correct version is to create a new table and then append rows. It's a bit more steps but it guaranteed to be correct. 450 may not be right.

To do this:
1) create a new table from the old table (same structure), pick the right format and save the table.
2) Then append all the rows from the original to the new.  This will make all the records go through our transaction code which decides on the version based on the data.
3) You then do have to save the table as the appends are edits.
The reason Save Table as does not do the versioning correctly is that it does not create transactions.  The table is written and not even open.
Perhaps a feature request could allow this to happen automatically. However, if you wanted the saved copy to have the same name as the original in a different folder, other changes would have to occur.
​

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 06-25-2019 15:14
From: Andrei Veselov
Subject: Save As Native Tab stamps it as v15.2

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well.

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Yes the ​copy/paste will give you the same results in general.  The copying of data is done with internal knowledge.
However, that works via the windows clipboard which means we have to copy data to and from that subsystem. 
Append works internally.
Also one advantage is that the append approach can be scripted in MapBasic or a tool.
.

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY
------------------------------

Original Message:
Sent: 07-03-2019 08:00
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Thanks Eric
That makes sense.
Would a Select All > Copy > Paste into the new table have the same effect?


------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 07-01-2019 16:46
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Another guaranteed safe way to get the correct version is to create a new table and then append rows. It's a bit more steps but it guaranteed to be correct. 450 may not be right.

To do this:
1) create a new table from the old table (same structure), pick the right format and save the table.
2) Then append all the rows from the original to the new.  This will make all the records go through our transaction code which decides on the version based on the data.
3) You then do have to save the table as the appends are edits.
The reason Save Table as does not do the versioning correctly is that it does not create transactions.  The table is written and not even open.
Perhaps a feature request could allow this to happen automatically. However, if you wanted the saved copy to have the same name as the original in a different folder, other changes would have to occur.
​

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 06-25-2019 15:14
From: Andrei Veselov
Subject: Save As Native Tab stamps it as v15.2

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well.

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

I wanted to do a test ​before saying something that may have changed. But I just tested it. So Copy/Paste will work but the memory consumption difference with append could be huge. I just tried a large table and copy to clipboard failed. MapInfo Pro had allocated over 5 gig of memory. 
The same table done via append never moved the memory much. It all stayed steady at about 450 Meg. It has a progress bar as well.
So I would say that Append is a much better approach but the difference may not be significant in your case.

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY
------------------------------

Original Message:
Sent: 07-03-2019 08:53
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Yes the ​copy/paste will give you the same results in general.  The copying of data is done with internal knowledge.
However, that works via the windows clipboard which means we have to copy data to and from that subsystem.
Append works internally.
Also one advantage is that the append approach can be scripted in MapBasic or a tool.
.

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 07-03-2019 08:00
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Thanks Eric
That makes sense.
Would a Select All > Copy > Paste into the new table have the same effect?


------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 07-01-2019 16:46
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Another guaranteed safe way to get the correct version is to create a new table and then append rows. It's a bit more steps but it guaranteed to be correct. 450 may not be right.

To do this:
1) create a new table from the old table (same structure), pick the right format and save the table.
2) Then append all the rows from the original to the new.  This will make all the records go through our transaction code which decides on the version based on the data.
3) You then do have to save the table as the appends are edits.
The reason Save Table as does not do the versioning correctly is that it does not create transactions.  The table is written and not even open.
Perhaps a feature request could allow this to happen automatically. However, if you wanted the saved copy to have the same name as the original in a different folder, other changes would have to occur.
​

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 06-25-2019 15:14
From: Andrei Veselov
Subject: Save As Native Tab stamps it as v15.2

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well.

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Eric - thanks for another gem.
The explanation of the difference between Append and a copy/paste was well worth asking the question.
You're right, the difference may not be significant on a small test but massive in reality.

Cheers

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Original Message:
Sent: 07-03-2019 09:44
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

I wanted to do a test ​before saying something that may have changed. But I just tested it. So Copy/Paste will work but the memory consumption difference with append could be huge. I just tried a large table and copy to clipboard failed. MapInfo Pro had allocated over 5 gig of memory.
The same table done via append never moved the memory much. It all stayed steady at about 450 Meg. It has a progress bar as well.
So I would say that Append is a much better approach but the difference may not be significant in your case.

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 07-03-2019 08:53
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Yes the ​copy/paste will give you the same results in general.  The copying of data is done with internal knowledge.
However, that works via the windows clipboard which means we have to copy data to and from that subsystem.
Append works internally.
Also one advantage is that the append approach can be scripted in MapBasic or a tool.
.

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 07-03-2019 08:00
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Thanks Eric
That makes sense.
Would a Select All > Copy > Paste into the new table have the same effect?


------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 07-01-2019 16:46
From: Eric Blasenheim
Subject: Save As Native Tab stamps it as v15.2

Another guaranteed safe way to get the correct version is to create a new table and then append rows. It's a bit more steps but it guaranteed to be correct. 450 may not be right.

To do this:
1) create a new table from the old table (same structure), pick the right format and save the table.
2) Then append all the rows from the original to the new.  This will make all the records go through our transaction code which decides on the version based on the data.
3) You then do have to save the table as the appends are edits.
The reason Save Table as does not do the versioning correctly is that it does not create transactions.  The table is written and not even open.
Perhaps a feature request could allow this to happen automatically. However, if you wanted the saved copy to have the same name as the original in a different folder, other changes would have to occur.
​

------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY

Original Message:
Sent: 06-25-2019 15:14
From: Andrei Veselov
Subject: Save As Native Tab stamps it as v15.2

Josh,

Block size should not have any effect on the TAB file version. Even older versions of Pro can handle different block sizes well.

Andrei

------------------------------
Andrei Veselov
PITNEY BOWES SOFTWARE, INC
Troy NY

Original Message:
Sent: 06-25-2019 02:31
From: Joshua Knight
Subject: Save As Native Tab stamps it as v15.2

Hi John

Separate to the NATIVEX/Extended tab, they also increased the blocksize. You can specify the old size (512) mapbasic to downgrade it. I'm not aware of a UI option for it.

Commit Table TABLE_TO_SAVE As "C:\myfolderpath...\newtablefilename.tab" TYPE NATIVE Charset "WindowsLatin1" blocksize 512 Interactive

My guess is this is causing the 15.2 version.

------------------------------
Joshua Knight
Datamine
Kew

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK
------------------------------

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Risky, isn't it!  If you have time to add it to the Portal that would be great please.  Many thanks!

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK
------------------------------

Original Message:
Sent: 04-29-2021 06:46
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Could it depend on the source table you are saving into a new table?
I could imagine a NativeX by default would be saved into a NativeX no matter the preference you have set.

If it's a Native table and your preference is to always create Native tables by default, I'd say you should get that. If that's not the case, it's more a bug than a feature request.

I haven't checked myself what happens for the specific circumstances

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------

Original Message:
Sent: 04-29-2021 06:53
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Risky, isn't it!  If you have time to add it to the Portal that would be great please.  Many thanks!

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 06:46
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Thanks Peter.  I had thought that, but it happens with Native tables.  I think it depends on what was saved last.  So if I last Saved As a table as Native, the next time I do Save As of a Native table it is Native by default.  If I Save As with a NativeX table, the next time Save As is by default MapInfo Extended, even if using a Native table.  So it does sound like a bug to me.

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK
------------------------------

Original Message:
Sent: 04-29-2021 07:05
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

Could it depend on the source table you are saving into a new table?
I could imagine a NativeX by default would be saved into a NativeX no matter the preference you have set.

If it's a Native table and your preference is to always create Native tables by default, I'd say you should get that. If that's not the case, it's more a bug than a feature request.

I haven't checked myself what happens for the specific circumstances

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 04-29-2021 06:53
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Risky, isn't it!  If you have time to add it to the Portal that would be great please.  Many thanks!

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 06:46
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

OK, sound as if the filetype list is sticky and remembers the last used filetype.
Let me give it a try and see how it works for me

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------

Original Message:
Sent: 04-29-2021 07:52
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Thanks Peter.  I had thought that, but it happens with Native tables.  I think it depends on what was saved last.  So if I last Saved As a table as Native, the next time I do Save As of a Native table it is Native by default.  If I Save As with a NativeX table, the next time Save As is by default MapInfo Extended, even if using a Native table.  So it does sound like a bug to me.

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 07:05
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

Could it depend on the source table you are saving into a new table?
I could imagine a NativeX by default would be saved into a NativeX no matter the preference you have set.

If it's a Native table and your preference is to always create Native tables by default, I'd say you should get that. If that's not the case, it's more a bug than a feature request.

I haven't checked myself what happens for the specific circumstances

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 04-29-2021 06:53
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Risky, isn't it!  If you have time to add it to the Portal that would be great please.  Many thanks!

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 06:46
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

I had confirmation from engineering. @William Wemple reached out and told me that the filetype list is sticky. During the session, it will remember the last file type you used.​

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------

Original Message:
Sent: 04-29-2021 09:20
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

OK, sound as if the filetype list is sticky and remembers the last used filetype.
Let me give it a try and see how it works for me

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 04-29-2021 07:52
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Thanks Peter.  I had thought that, but it happens with Native tables.  I think it depends on what was saved last.  So if I last Saved As a table as Native, the next time I do Save As of a Native table it is Native by default.  If I Save As with a NativeX table, the next time Save As is by default MapInfo Extended, even if using a Native table.  So it does sound like a bug to me.

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 07:05
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

Could it depend on the source table you are saving into a new table?
I could imagine a NativeX by default would be saved into a NativeX no matter the preference you have set.

If it's a Native table and your preference is to always create Native tables by default, I'd say you should get that. If that's not the case, it's more a bug than a feature request.

I haven't checked myself what happens for the specific circumstances

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 04-29-2021 06:53
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Risky, isn't it!  If you have time to add it to the Portal that would be great please.  Many thanks!

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 06:46
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------

Original Message:
Sent: 5/4/2021 3:57:00 AM
From: Peter Horsbøll Møller
Subject: RE: Save As Native Tab stamps it as v15.2

I had confirmation from engineering. @William Wemple reached out and told me that the filetype list is sticky. During the session, it will remember the last file type you used.​

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------

Original Message:
Sent: 04-29-2021 09:20
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

OK, sound as if the filetype list is sticky and remembers the last used filetype.
Let me give it a try and see how it works for me

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 04-29-2021 07:52
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Thanks Peter.  I had thought that, but it happens with Native tables.  I think it depends on what was saved last.  So if I last Saved As a table as Native, the next time I do Save As of a Native table it is Native by default.  If I Save As with a NativeX table, the next time Save As is by default MapInfo Extended, even if using a Native table.  So it does sound like a bug to me.

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 07:05
From: Peter Horsbøll Møller
Subject: Save As Native Tab stamps it as v15.2

Could it depend on the source table you are saving into a new table?
I could imagine a NativeX by default would be saved into a NativeX no matter the preference you have set.

If it's a Native table and your preference is to always create Native tables by default, I'd say you should get that. If that's not the case, it's more a bug than a feature request.

I haven't checked myself what happens for the specific circumstances

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 04-29-2021 06:53
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Risky, isn't it!  If you have time to add it to the Portal that would be great please.  Many thanks!

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 04-29-2021 06:46
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

Ugh!
Mine does that too.
Sounds like a request for the Ideas Portal...
Shall I ? Or will you?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom

Original Message:
Sent: 04-29-2021 05:42
From: Jane Mason
Subject: Save As Native Tab stamps it as v15.2

Hello John, I thought I would ask my question here as it is all related.  I had a problem with not being able to open tables created in v2019.3 in v15.0 or other applications, and realised that although in my System Settings 'New Table' is set by default to MapInfo rather than MapInfo Extended (see attached image) when I do Save Copy As, 'Save As Type' defaults to MapInfo Extended.  After so many years as a user I don't always remember to check this!  And this happens with Query tables from Native tab and Extended tab.  Hopefully I'm getting into the habit of checking now.

So my question is - Is there anywhere where Save Copy As can be set to MapInfo rather than MapInfo Extended by default?

Many thanks,
Jane

------------------------------
Jane Mason
Biological Records Officer (GIS), Suffolk Biodiversity Information Service, UK

Original Message:
Sent: 06-24-2019 12:26
From: John Ievers
Subject: Save As Native Tab stamps it as v15.2

I have set my preferences in MapInfo to Extended tab as default but needed to share this table with a colleague using v15.0.
So I Saved As a Native tab.
However, the tab is stamped as v15.2 and prompts to use that version.
How do I share my data with my 32-bit colleague?

------------------------------
John Ievers
CDR Group
Hope Valley, United Kingdom
------------------------------