stop Numbers converting text to numbers when importing into text columns

I have a text file (utf-8) containing tab-separated fields exported from a data base.

I set up a new table in Numbers, and explicitly set all the cells in all the columns to be of data format text.

Then I copy the text from the text file, and paste it into the table.

Any field that contained a text that could possibly be interpreted as a number, is converted to a number and the data format of that cell is changed to number.

How can I switch off or avoid this undesired interpretation that Numbers does?

Some fields contain postal codes, and some of these postal codes look like numbers, but have significant leading zeroes. They are text, but Numbers insists on interpreting them as numbers and throws away the leading zeros. The resulting table is useless.

Example:

if the text file contains the lines

Sergy <tab> FR <tab> 01770

Meyrin <tab> CH <tab> 1217

as in:

then after pasting, the table shows

Sergy FR 1770

Meyrin CH 1217

as in:

and this is of course wrong.

The problem did not exist in the '09 versions of Numbers.


Posted on Feb 4, 2022 12:24 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 4, 2022 7:40 AM

I feel your pain. You are far from the first to complain about how Numbers is too "smart" when importing, to the point of being dumb. It was that way in Numbers '09 also, just different. Here is a script that might help. It creates a new Numbers document, formats all the cells in the table to text, and imports all CSV fields as text.


  1. Open the Script Editor app
  2. Copy/paste the script from below into Script Editor
  3. Use the Play button to run the script.


If you like it,

  1. Save it with a short descriptive name. The default location is your user Library/Scripts folder. It needs to go there.
  2. Go to Script Editor->Preferences
  3. Check the box to show scripts menu in menu bar
  4. A scroll icon will appear in the upper right side of the menu at the top of the screen, near bluetooth, wifi, etc.
  5. Click on it and you should see your script listed. You can run it from there.


-- Import CSV File into Numbers

-- This script reads a user-selected CSV file, creates a new Numbers document, and
-- imports the contents of the CSV file into the Numbers document with all cells formatted as text.

-- The usual/simple way of separating CSV text into "items" by setting the text item delimiter to a comma
-- doesn't work in all cases because CSV files can contain commas within quoted text.  To get around this,
-- the algorithm first converts the file to a "Unicode character 0000" delimited string as it interprets the file and determines
-- which commas are within quoted text and which are the actual separators. 
-- This means that "Unicode character 0000" is not an unallowable character in the CSV file.
-- Carriage return is not an allowed character in a CSV field, even if surrounded by quotes.
-- The user can choose the CSV delimiter, though that code is commented out at this time

-- Written by Badunit,  reusing some code from others
-- Last updated Feb 4, 2022

set newTID to character id 0 --Unicode character 0000
set oldTID to AppleScript's text item delimiters


set csvFile to (choose file of type "CSV")
set csvText to read csvFile

-- If want user to select comma or semicolon as delimiter, swap the commenting of the next two lines 
set csvDelimiter to ","
--set csvDelimiter to (choose from list {",", ";"} with title "Delimiter" with prompt "Choose a delimiter" default items ",") as text

-- Convert the CSV text to delimited string with the specified delimiter. 
-- First turn it into an array of characters for easy mainipulation.
-- Pad the end with a null for the "quote test" portion of the algorithm.
-- Before converting back to a string, set the Applescript text delimiters to null so that no delimiters are put between characters

set theCharacters to characters of csvText
set end of theCharacters to ""

set i to 1
set openquote to false

repeat while i ≤ length of csvText
	if item i of theCharacters = "\"" then
		if openquote = true then
			if item (i + 1) of theCharacters = "\"" then
				set i to i + 1
			else
				set openquote to false
			end if
		else
			set openquote to true
			
		end if
		
		set item i of theCharacters to ""
	else if item i of theCharacters = csvDelimiter and openquote = false then
		set item i of theCharacters to newTID
	end if
	set i to i + 1
end repeat

set AppleScript's text item delimiters to ""
set newText to theCharacters as string

-- Count paragraphs (rows in spreadsheet) and text items (columns in spreadsheet)
-- Use maximum number of text items to set number of columns, rather than add extra columns on the fly.

set AppleScript's text item delimiters to newTID

set rowCount to (count paragraphs in newText)
set maxColumns to 0
repeat with x from 1 to rowCount
	set columnCount to count text items in paragraph x of newText
	if columnCount > maxColumns then set maxColumns to columnCount
end repeat

--Create new Numbers document with correct sized table
--Set format of all cells to Text

tell application "Numbers"
	activate
	make new document at front
	delay 1
	tell document 1
		tell sheet 1
			delete every table
			make new table at front with properties ¬
				{row count:rowCount, column count:maxColumns, header column count:0, header row count:0}
			set format of every cell of table 1 to text
		end tell
	end tell
end tell

--Loop through paragraphs and delimited items of newText and place them in the correponding 
-- cells in the newly created table

repeat with nextRow from 1 to rowCount
	set columnCount to (count text items in paragraph nextRow of newText)
	repeat with nextColumn from 1 to columnCount
		set nextValue to text item nextColumn of paragraph nextRow of newText
		tell application "Numbers" to tell document 1 to tell sheet 1 to tell table 1
			set nextCell to cell nextColumn of row nextRow
			set value of nextCell to nextValue
		end tell
	end repeat
end repeat

-- Clean up. Set the delimiters back to what they were at the start

set AppleScript's text item delimiters to oldTID














Similar questions

20 replies
Question marked as Top-ranking reply

Feb 4, 2022 7:40 AM in response to RobertCailliau

I feel your pain. You are far from the first to complain about how Numbers is too "smart" when importing, to the point of being dumb. It was that way in Numbers '09 also, just different. Here is a script that might help. It creates a new Numbers document, formats all the cells in the table to text, and imports all CSV fields as text.


  1. Open the Script Editor app
  2. Copy/paste the script from below into Script Editor
  3. Use the Play button to run the script.


If you like it,

  1. Save it with a short descriptive name. The default location is your user Library/Scripts folder. It needs to go there.
  2. Go to Script Editor->Preferences
  3. Check the box to show scripts menu in menu bar
  4. A scroll icon will appear in the upper right side of the menu at the top of the screen, near bluetooth, wifi, etc.
  5. Click on it and you should see your script listed. You can run it from there.


-- Import CSV File into Numbers

-- This script reads a user-selected CSV file, creates a new Numbers document, and
-- imports the contents of the CSV file into the Numbers document with all cells formatted as text.

-- The usual/simple way of separating CSV text into "items" by setting the text item delimiter to a comma
-- doesn't work in all cases because CSV files can contain commas within quoted text.  To get around this,
-- the algorithm first converts the file to a "Unicode character 0000" delimited string as it interprets the file and determines
-- which commas are within quoted text and which are the actual separators. 
-- This means that "Unicode character 0000" is not an unallowable character in the CSV file.
-- Carriage return is not an allowed character in a CSV field, even if surrounded by quotes.
-- The user can choose the CSV delimiter, though that code is commented out at this time

-- Written by Badunit,  reusing some code from others
-- Last updated Feb 4, 2022

set newTID to character id 0 --Unicode character 0000
set oldTID to AppleScript's text item delimiters


set csvFile to (choose file of type "CSV")
set csvText to read csvFile

-- If want user to select comma or semicolon as delimiter, swap the commenting of the next two lines 
set csvDelimiter to ","
--set csvDelimiter to (choose from list {",", ";"} with title "Delimiter" with prompt "Choose a delimiter" default items ",") as text

-- Convert the CSV text to delimited string with the specified delimiter. 
-- First turn it into an array of characters for easy mainipulation.
-- Pad the end with a null for the "quote test" portion of the algorithm.
-- Before converting back to a string, set the Applescript text delimiters to null so that no delimiters are put between characters

set theCharacters to characters of csvText
set end of theCharacters to ""

set i to 1
set openquote to false

repeat while i ≤ length of csvText
	if item i of theCharacters = "\"" then
		if openquote = true then
			if item (i + 1) of theCharacters = "\"" then
				set i to i + 1
			else
				set openquote to false
			end if
		else
			set openquote to true
			
		end if
		
		set item i of theCharacters to ""
	else if item i of theCharacters = csvDelimiter and openquote = false then
		set item i of theCharacters to newTID
	end if
	set i to i + 1
end repeat

set AppleScript's text item delimiters to ""
set newText to theCharacters as string

-- Count paragraphs (rows in spreadsheet) and text items (columns in spreadsheet)
-- Use maximum number of text items to set number of columns, rather than add extra columns on the fly.

set AppleScript's text item delimiters to newTID

set rowCount to (count paragraphs in newText)
set maxColumns to 0
repeat with x from 1 to rowCount
	set columnCount to count text items in paragraph x of newText
	if columnCount > maxColumns then set maxColumns to columnCount
end repeat

--Create new Numbers document with correct sized table
--Set format of all cells to Text

tell application "Numbers"
	activate
	make new document at front
	delay 1
	tell document 1
		tell sheet 1
			delete every table
			make new table at front with properties ¬
				{row count:rowCount, column count:maxColumns, header column count:0, header row count:0}
			set format of every cell of table 1 to text
		end tell
	end tell
end tell

--Loop through paragraphs and delimited items of newText and place them in the correponding 
-- cells in the newly created table

repeat with nextRow from 1 to rowCount
	set columnCount to (count text items in paragraph nextRow of newText)
	repeat with nextColumn from 1 to columnCount
		set nextValue to text item nextColumn of paragraph nextRow of newText
		tell application "Numbers" to tell document 1 to tell sheet 1 to tell table 1
			set nextCell to cell nextColumn of row nextRow
			set value of nextCell to nextValue
		end tell
	end repeat
end repeat

-- Clean up. Set the delimiters back to what they were at the start

set AppleScript's text item delimiters to oldTID














Feb 4, 2022 8:01 AM in response to Badunit

-- Import CSV File into Numbers

-- This script reads a user-selected CSV file, creates a new Numbers document, and
-- imports the contents of the CSV file into the Numbers document with all cells formatted as text.

-- The usual/simple way of separating CSV text into "items" by setting the text item delimiter to a comma or semicolon or
-- tab doesn't work in all cases because CSV files can contain the delimiter within quoted text.  To get around this,
-- the algorithm first converts the file to a "Unicode character 0000" delimited string as it interprets the file and determines
-- which "delimiters" are within quoted text and which are the actual delimiters. 
-- This means that "Unicode character 0000" is not an unallowable character in the CSV file.
-- Carriage return is a not an allowed character in a CSV field, even if surrounded by quotes.

-- Written by Badunit, reusing some code from others
-- Feb 4, 2022

set newTID to character id 0 --Unicode character 0000
set oldTID to AppleScript's text item delimiters


set csvFile to {choose file of type {"TXT", "CSV"}}
set csvText to read csvFile

set csvDelimiter to (choose from list {",", ";", "Tab"} with title "Delimiter" with prompt "Choose a delimiter" default items ",") as text
if csvDelimiter = "Tab" then set csvDelimiter to "	"

-- Convert the CSV text to delimited string with the specified delimiter. 
-- First turn it into an array of characters for easy mainipulation.
-- Pad the end with a null for the "quote test" portion of the algorithm.
-- Before converting back to a string, set the Applescript text delimiters to null so that no delimiters are put between characters

set theCharacters to characters of csvText
set end of theCharacters to ""

set i to 1
set openquote to false

repeat while i ≤ length of csvText
	if item i of theCharacters = "\"" then
		if openquote = true then
			if item (i + 1) of theCharacters = "\"" then
				set i to i + 1
			else
				set openquote to false
			end if
		else
			set openquote to true
			
		end if
		
		set item i of theCharacters to ""
	else if item i of theCharacters = csvDelimiter and openquote = false then
		set item i of theCharacters to newTID
	end if
	set i to i + 1
end repeat

set AppleScript's text item delimiters to ""
set newText to theCharacters as string

-- Count paragraphs (rows in spreadsheet) and text items (columns in spreadsheet)
-- Use maximum number of text items to set number of columns, rather than add extra columns on the fly.

set AppleScript's text item delimiters to newTID

set rowCount to (count paragraphs in newText)
set maxColumns to 0
repeat with x from 1 to rowCount
	set columnCount to count text items in paragraph x of newText
	if columnCount > maxColumns then set maxColumns to columnCount
end repeat

--Create new Numbers document with correct sized table
--Set format of all cells to Text

tell application "Numbers"
	activate
	make new document at front
	delay 1
	tell document 1
		tell sheet 1
			delete every table
			make new table at front with properties ¬
				{row count:rowCount, column count:maxColumns, header column count:0, header row count:0}
			set format of every cell of table 1 to text
		end tell
	end tell
end tell

--Loop through paragraphs and delimited items of newText and place them in the correponding 
-- cells in the newly created table

repeat with nextRow from 1 to rowCount
	set columnCount to (count text items in paragraph nextRow of newText)
	repeat with nextColumn from 1 to columnCount
		set nextValue to text item nextColumn of paragraph nextRow of newText
		tell application "Numbers" to tell document 1 to tell sheet 1 to tell table 1
			set nextCell to cell nextColumn of row nextRow
			set value of nextCell to nextValue
		end tell
	end repeat
end repeat

-- Clean up. Set the delimiters back to what they were at the start

set AppleScript's text item delimiters to oldTID





Feb 6, 2022 4:05 AM in response to RobertCailliau

Hi Robert,


I typed a subset of your data into TextEdit with tab separators and saved as CSV.

I opened the CSV in Pages with Menu > View > Show Invisibles.



Menu > Edit Find > Find... (command F)

Type \t into the Find field. (\t is the code for the tab character).

Type \t| into the Replace field (| is the "pipe character that does not appear in your CSV).

Click on the right arrow (bottom right) to initiate the Find & Replace dialogue.



Click on Replace All



Dismiss the Find & Replace dialogue. Select All and Copy.

Go to Numbers and create a table that is formatted as Text. No Header Row or Header Column for now.

Click once in the top left cell and Paste.


Duplicate the table.

Column A is correct (no preceding "|")

Formula in B1: RIGHT(Table 1::B1,LEN(Table 1::B1)−1)

Fill down and fill right



The leading zeroes are preserved.


Regards,

Ian.


Feb 6, 2022 6:13 AM in response to RobertCailliau

Here's another take on the insert | character, import into Numbers, then remove | character, using the Shortcuts app.


1 - Open the tabbed data exported by the database in TextEdit or whatever.


2 - Open the Shortcuts app and drag in Replace Text and Copy to Clipboard actions.


3 - Copy-paste an (invisible) tab from the data in TextEdit and paste after 'Replace' and again after 'with'. Add | after the tab after 'with'.




4 - Select all data open in TextEdit, command-c, run the Shortcut.


5 - Click in Numbers, and command-v to paste.


6 - Select cells in Numbers, type command-f, type | in the Search box and leave the Replace box blank. Click 'Replace All'.




Result:





SG



Feb 4, 2022 3:49 AM in response to RobertCailliau

RobertCailliau wrote:

I suspect that what happens is that Numbers does the interpretation before the paste, why else would it go wrong when I ask to match style?


Yes, that is my guess too. A few versions back the behavior when pasting CSV text changed. It seems the idea was to make Numbers smarter and more "helpful." But it in some cases it became too smart and started guessing wrong, e.g. assuming that what looks like a number must be a number.


Do you have any control over what the database exports? If you can get it to use comma as delimiter and surround all values by " " then you can try this workaround.


After pasting, choose click the Adjust Settings box that pops up, go to Advanced Settings and set Text Qualifier to None, giving you something like this.





Then set up new columns with formulas to strip the surrounding quotes.




Not ideal, but it might get the job done.


Another option, if you have to do this often, might be an AppleScript that reads the clipboard and sets the values in Numbers cells.


SG




Feb 5, 2022 2:09 AM in response to RobertCailliau

Found a stupid and not foolproof way, which at least works in most practical cases, though it is to be used with precaution.

Pick a character that does not occur in the data. This can be something convoluted (unicode is large...)

In my case, the character "|" (vertical bar) does not occur.

So: with a text editor like BBEdit, replace "tab0" with "tab|0" (and also "return0" with "return|0" should the first column potentially have data with leading zeroes)

Then open with Numbers, make all columns text, replace all "|" with nothing.

This is fairly fast and fairly reliable.

There may also be cases where a trailing zero must be preserved, e.g. 75.00. This may be the case in data like serial numbers, bank account numbers and such, where the trailing zero is significant, but the data look like a number with decimals. The same trick would work. For data enclosed in quotes, the replacement would be somewhat different, but obvious to you.


Fortunately the weather is very nice right now.

Feb 5, 2022 3:02 AM in response to RobertCailliau

RobertCailliau wrote:

I could first paste, then sort the table by country code, and then put the zeroes back as per your recipe.

But it is yet more complex: the records also contain telephone numbers, some of which start with one or two zeroes.


You can restore the original lengths, with a different length for each country, with a formula like this. A pain. We shouldn't have to do it. But the native parser is of course much faster than a script, and it then becomes a question of fixing just the columns that have leading 0s. One formula per column. Not as laborious as sorting and such.




=NUMTOBASE(C2,10,XLOOKUP(B2,{"FR","CH","AT"},{5,4,4},"Not found"))&""


Or for regions that use the comma as a decimal separator:


=NUMTOBASE(C2;10;XLOOKUP(B2;{"FR"."CH"."AT"};{5.4.4};"Not found"))&""


The &"" at the end coerces to Text.


A similar approach (I think) can be used for phone numbers with leading zeros though it may not work if they're formatted with spaces in the middle.


Or something like this for phone numbers (not perfect, but close).



SG


Feb 4, 2022 10:50 AM in response to Badunit

Hi Badunit:


(I think in the past you replied to some other posts of mine too).

Thanks very much for the effort put into the scripts...

:-)


The database can easily be asked to produce CSV with quotes instead of tabs, etc.

The script is very readable. I will try it.


Of course, (knowing you and knowing me) I could not resist to write a small LiveCode program:

its interface has a single button and a single table field. The code for the button is:



The fist line prompts the user to select a file (using the Finder's selection dialog), the file path is returned in the result variable "it". The second line then uses "it" to read the file, convert it to unicode (utf-8 not being unicode, but a compression of unicode) and dump it into the one and only field which spreads it, using the tabs, over its columns.

The program's interface looks like:



(but I had to blur the data in some columns of course)

and a close-up of a small section of the postcode column (elsewhere in the list) looks like this:



Zeroes still there (of course).


Not at all to belittle your effort in AppleScript, but making that program literally took only a minute or two.

However, it does not solve the problem, which is that of switching OFF an undesired interference.

Your script solves the specific problem. The general one remains: I will have to be careful whenever I paste something into a Numbers table.


As I always say: "before we reach the pinnacles of Artificial Intelligence, we will have to cross the desert of half-witted entities."


Thanks both, have a nice weekend.

Feb 4, 2022 3:10 AM in response to SGIII

Yes, SG, I have in fact already given Apple a bug report about this.


And sorry, but on these forums, not just the Apple one, and not just my own questions, I find that often the first answer is "why do you want to do that?" .

Your answer was at least an attempt to help, I appreciate that.

The second answers on such forums are too quick reactions.

Then, and I fully admit that, I sometimes do not express myself clearly. I spent a great deal of time crafting the question.

So let's go through this again:


"I have a text file (utf-8) containing tab-separated fields exported from a data base."

that means I do not have much control over how this comes out, and there should be no need either. It's just a set of lines, with fields all being text. The data base does not contain any other fields than text. No dates, no numbers, just utf-8 text, with tabs between the fields and returns between the records.


"I set up a new table in Numbers, and explicitly set all the cells in all the columns to be of data format text."

So now Numbers should not change whatever I paste, especially not if what is pasted is pure, simple, unformatted text.

And most certainly it should not do so if I "Paste and match Style". But it does.

I suspect that what happens is that Numbers does the interpretation before the paste, why else would it go wrong when I ask to match style? Although it could be argued that cell format is not part of the style.


The example mentions postal codes, but that is because it's the obvious one where it goes wrong.

And indeed, Meyrin is in Switzerland and Sergy in France (actually Sergy's postal code is 01401, I made a mistake, but it is irrelevant here). There are also lines with UK post codes (which definitely are text), a Brazilian one and so on.

For the specific example of the postal code problem, I could first paste, then sort the table by country code, and then put the zeroes back as per your recipe. However, even in that case it is more complex: not all French postal codes start with 0. Therefore I would have to select the lines with French addresses and sort those by code and then restore the zeroes only for those codes that are less than 10000 (the codes do all have five digits).

But it is yet more complex: the records also contain telephone numbers, some of which start with one or two zeroes.


In any case, Numbers should not do anything behind my back.

If I find a simple solution, I'll post it here.


Thanks again,

Feb 4, 2022 10:12 PM in response to RobertCailliau

RobertCailliau wrote:

(2) Open Office misbehaves in exactly the same way.
:-(


You're probably already aware that by default Excel also treats text that looks like Numbers as numbers.


But when you split into columns using the Text to Columns wizard you can define the data format for each column. Here I selected the third column and chose Text.




That preserves the text in Excel. But when you copy-paste from Excel into Numbers the designation as Text is not respected.


SG


Feb 6, 2022 11:39 AM in response to Yellowbox

SGIII:

:-)

Sure, but very complex and needs another table to look up the country codes. Members can live anywhere in the world...

Plus, remember, not all French codes start with a zero. I don't know about the situation in all other countries, it may be complex.

But thanks for the ideas.

Your second thought is more or less what I did in the end, and I could automated it with Keyboard Maestro, hanging it off a single keystroke that would only be active in Numbers.


I hope Apple will provide a setting with which to turn OFF any so-called intelligence when pasting.

That's the only thing that will work in all cases. Sigh. See also below:


Yellobox:

Thanks, yes, well that is of course exactly what I did, but even simpler because I told Numbers to replace the "|" with nothing, so no second table needed. But though this remedy works in this particular case, it is not general.

I am now in fact worried that whenever I paste something into a Numbers table, there may be some "intelligent" interpretation that fouls up some datum somewhere, and it will be discovered only much later.

Let me tell you about an old bug in Excel: I was running on a Powerbook 170 (yes, 40Mb hard disc) and stored the licence codes of my applications in an Excel sheet. Then Wolfram wanted confirmation for its Mathematica program. I looked up the code in the sheet, but... the original code was a list of 4 digit numbers separated by hyphens. Excel had dutifully performed the subtractions, but I had not noticed. That cost me the full price for Mathematica again. I think I have seen something similar in Numbers, but can't reproduce it right now.


Feb 4, 2022 2:03 AM in response to SGIII

Thanks, but that cannot possibly be the solution:

The postal code for Sergy is 01770, with a zero.

The postal code for Meyrin is 1217. No zero.

I thought that was clear from the example.

The problem is NOT about restoring leading zeroes (your proposal introduces a data error).

It is about telling Numbers NOT to interpret the character string "01770" as if it were a number, especially when I have explicitly set the cell format to "text".

Even when I select "Paste and match style", Numbers 11.x STILL insists on interpreting "01770" as if it were a number, removes the zero, and THEN pastes it into a text cell.

It looks like this is a BUG, unless there is some setting or preference that I have overlooked, and I thought maybe someone could help me find that preference or setting.

Feb 4, 2022 2:33 AM in response to RobertCailliau

Well, you did after all mention dropping leading 0s in your post.😀 Postal code systems vary widely throughout the world. I haven't seen a system where the codes have varying lengths, and didn't realize the two codes were from different countries, so I assumed the goal was to have five characters throughout. Sorry about that.


As illustrated, you can easily set the length of any particular code via the Numeral System Date Format. If you do not want to add leading zeros to Meyrin (and to other codes for the same country) then you can just set Places to 4 for those. So the data you bring in does not result in a "useless" table. Rather it is a table that needs a little further processing as described.


Keep in mind we are your fellow users here, trying to help others use the software as it is now. If the current behavior does not meet your needs, then you should consider giving feedback directly to Apple via Numbers > Provide Numbers Feedback in the menu.


SG







Feb 4, 2022 4:20 AM in response to SGIII

Totally agreed that many of today's apps are too "smart". It's OK if I can switch it all off, so I was looking for a setting but there is apparently none.

As an example of our frustrations here: because of where we live, we talk and write in something locally known as "franglais". It means we just use the French or the English word, whatever is more convenient, plus there are so many acronyms. The result is that we cannot ever use spelling checkers. "Check spelling while typing" is one of the nightmares. In some apps it cannot be switched off, or comes on again the next time it is launched.


But back to our problem: your suggestions do solve the problem but they are indeed a laborious workaround.

Yes, I can tell the data base to put quotes, but then it doubles up or escapes quotes that appear in the texts. I thought of writing an applescript too. Again laborious, needs to be maintained, debugged, might have a bug that only shows up after a long time, or warps the result in a way difficult to detect.

It's just infuriating that pasting plain text is no longer possible.

Fortunately I still have a machine running the old Numbers, but again that is laborious.

Maybe I should move to Linux... A whole new world of pain.

Or pass via Open Office? (another world of pain).


And yet another example of a text problem: I'm doing this database stuff to help an association of retired people. One of them has the surname " 't Hart ". Yes you read that right: apostrophe-lowercase t-space-Hart.

You can guess how difficult it was to get that into the data base, to sort, to search etc. unless you can switch all semi-intelligence off.

Have a good day.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

stop Numbers converting text to numbers when importing into text columns

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.