MapInfo Pro

In MapInfo 2023 it automatically gets recognized as char and also gets opened that way. Maybe you are using an older version?

Hi Paolo

That sounds like a bug but not something I have noticed earlier. 

MapInfo Pro should, of course, honor the column type you select when opening an Excel file.

Do you get this misbehavior with a small file with just 6 records as you show above or only if you have thousands of records where the first many records are numerical?

The table has over 18000 rows. I attach an example so you can check if this happens to you also

Hi Paolo

That sounds like a bug but not something I have noticed earlier. 

MapInfo Pro should, of course, honor the column type you select when opening an Excel file.

Do you get this misbehavior with a small file with just 6 records as you show above or only if you have thousands of records where the first many records are numerical?

It works here, if I change the float to char, MapInfo decides for a char(19) and it keeps that field definition after opening the table.

If it still fails for you, you can just close the file, edit the TAB file header and then open the TAB again.

The table has over 18000 rows. I attach an example so you can check if this happens to you also

Hi Paolo

That sounds like a bug but not something I have noticed earlier. 

MapInfo Pro should, of course, honor the column type you select when opening an Excel file.

Do you get this misbehavior with a small file with just 6 records as you show above or only if you have thousands of records where the first many records are numerical?

Morning Uffe,

Can you check if the values look fine for you? Especially the values at the end of the table. I want to verify if the issue I described below where the values starting with characters got lost can be replicated.

Thanks

It works here, if I change the float to char, MapInfo decides for a char(19) and it keeps that field definition after opening the table.

If it still fails for you, you can just close the file, edit the TAB file header and then open the TAB again.

The table has over 18000 rows. I attach an example so you can check if this happens to you also

Hi Paolo

That sounds like a bug but not something I have noticed earlier. 

MapInfo Pro should, of course, honor the column type you select when opening an Excel file.

Do you get this misbehavior with a small file with just 6 records as you show above or only if you have thousands of records where the first many records are numerical?

The table has over 18000 rows. I attach an example so you can check if this happens to you also

Hi Paolo

That sounds like a bug but not something I have noticed earlier. 

MapInfo Pro should, of course, honor the column type you select when opening an Excel file.

Do you get this misbehavior with a small file with just 6 records as you show above or only if you have thousands of records where the first many records are numerical?

OK, it seems to work but then it doesn't.

We convert the column to Char as specified but the values are all numbers - all the characters seem to have been removed from the table once loaded into MapInfo Pro. The values starting with a character seem to have been changed into an empty string.

If I format the cells in the first row as Text, MapInfo Pro detects this and suggests using Char(20) as the column type.

Here you can see the result

I'd recommend raising a case with our support team on opening the Excel file and changing the column type to char. You can send an email to our support team at support@precisely.com

Thanks

The table has over 18000 rows. I attach an example so you can check if this happens to you also

Hi Paolo

That sounds like a bug but not something I have noticed earlier. 

MapInfo Pro should, of course, honor the column type you select when opening an Excel file.

Do you get this misbehavior with a small file with just 6 records as you show above or only if you have thousands of records where the first many records are numerical?