MapInfo Pro

Hi,

A client has a TAB file that was created in 64 bit and receives the following error message when attempting to open in 32 bit:

See Attachment

The TAB is well under the 2GB limit and has only one polygon with one column in the table.

I saved the TAB as a new TAB and still won't open. I did manage to open it in 32 bit when creating a new TAB and did copy/paste to the polygon.

Any ideas?

I've attached the TAB as well.

Thanks!

I want to add that in this Testing file I can also change the !version 1520 to !version 1500 if I edit the .TAB file in a text editor and that will solve it. However, in the original file when I try that, it did not work.

Hi Kobi,

I can download the .dat, .id and the .map file but don't see the tab file attached. Could you please share it once again.

Thanks,

Shweta

Hi Kobi,

It looks like you have stumbled upon the workaround for editing the table version number via a text editor. :)

Various reasons why a table might inherit a particular version number of MapInfo Pro can be found under the Help menu topic "File Versions and TAB, MIF/MID, and WOR Support. I've pasted a screenshot below of this topic with a table which highlights the features from MapInfo Pro v15.2 which will cause a table version to inherit the 1520 table version.

See Attachment

Hope this helps to explain.

Dave

@Shweta Shukla?, here are the files again.

@Dave Kuo?, yes, the work around is a nice trip for WOR and TAB files, but as I said, in the original file this work around did not help. Do you know why this would be?

I apologize for the multiple answers. It wouldn't let me upload more than one file per response for some reason 😐

But that should be all 4 (tab, dat, id, map) once again

So you haven't saved it as an Extended Tab file (nativex) but I see that the character set is Windows Hebrew - is this a UTF8 or 16 character set? I don't know but this ?would set it apart from 32-bit operation.

@John Ievers?, the Windows Hebrew is it's own encoding, separate from UTF-8 and UTF-16 and works in 32-bit.

However, I see that the original file is NativeX/Extended TAB (screenshot from original TAB):

See Attachment

How do I avoid it saving the file as an Extended TAB?

This is a small file with one row and one column, so no reason to use Extended TAB.

Set the Options in your backstage area:- the first category is Systems Settings and bottom right of that dialog is an area for New Tables. Here you can set the table Format and Charset.?

You can also define standard tab or extended tab when you perform a Table >Save Copy As routine?

Thank you very much @John Ievers?!