How do you set the number of rows in a spreadsheet, so that even when you drag data in, in writes over those rows instead of adding a new row?

Question

How do you set the number of rows you want in a spreadsheet, so that even when you drag data in, in writes over those rows instead of adding a new row?

Answer 1

After the discovery reported above, I filed this report :
Bug ID# 10073038
Summary:
When Numbers is used on a system with decimal comma a csv file may be good AND wrong
Steps to Reproduce:
With Numbers v2, you introduced an interesting enhancement.
In system using the comma as decimal separator, Numbers requires csv files using the semi-colon as values delimiter.
In fact it’s true if we OPEN the document dragging its icon on Numbers one or thru the open dialog.
This said.
(1) Drag and drop a csv built with the 'semi-colon' standard on a table or on a sheet
(2) Drag and drop a csv built with the 'comma' standard on a table or on a sheet
Expected Results:
Every normally constituted user assume that in
case (1) he will get a perfectly built table
case (2) he will get every cells of a row in a single cell
Actual Results:
In fact you forgot the drag and drop way of use and in
case (1) every values separated by semi-colon are inserted in a single cell
case (2) values separated by comma are correctly spread in a table
isn’t it ridiculous ?
Regression:
Except looking in  QuickView to see which is exactly the structure of the file to decide the way we will insert it in a Numbers document, we may use an applescript fair enough to replace the semi-colons by TAB characters
or
to replace the commas by TABs and the decimal periods by commas
Notes:
While I am on this subject, I wish to make two proposals:
(1)  It would be fine to format the date according to the ISO format year-mm-dd when you export a Numbers doc to csv.
Doing that, dates would be imported correctly in every countries.
At this time, on an English system, you export as mm/dd/year.
If the doc is open on a system using the format dd/mm/year, the results will be odd.
On a system using the format dd/mm/year, you export this way and so, if the doc is open on a system using the format mm/dd/year the results are odd too.
As every localized versions accept the ISO format (at least on entry), using it in the export scheme would give a correct behavior everywhere.
(2) It would be fine to add the format Tab Separated Values in the Export pane.
TSV + ISO date format would give documents opening flawlessly everywhere.
Yvan KOENIG (VALLAURIS, France) dimanche 4 septembre 2011 21:27:41
iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
My iDisk is : <http://public.me.com/koenigyvan>
Please : Search for questions similar to your own before submitting them to the community