Issue 78337 - .csv files with >32K records not imported into Calc
Summary: .csv files with >32K records not imported into Calc
Status: CLOSED DUPLICATE of issue 75199
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.2 RC4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-12 13:26 UTC by gmichalk
Modified: 2007-07-10 15:47 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description gmichalk 2007-06-12 13:26:25 UTC
Opening/Importing large .csv files (>32K but <64K records) generates the message:

"The maximum number of rows has been exceeded. Excess rows were not imported."

Attached is the file gnr.zip, valid as of 5 June 07, which decompresses into two
.csv files, gnr_part1 and gnr_part2 (the latest version can be obtained from the
site http://www.gnb.nsw.gov.au/name/search - this file increases very slowly in
size - will substitute for the 5 June 07 version).

Attempting to Open either of these two files in Oo2.2 generates the above
message. Opening these files in Excel is successful - saving in .XLS format and
then Opening in Oo2.2 also works.

Diagnosis: Previous efforts to extend the maximum number of Rows in Calc from
32K to 64K ignored the issue of importing large .csv files.
Comment 1 pagalmes.lists 2007-06-12 23:08:33 UTC
The message "The maximum number of rows has been exceeded. Excess rows were not
imported." is displayed, but all the values are imported correctly.

Seems that this should be an easy2fix issue. What do you think?
Comment 2 gmichalk 2007-06-14 09:17:36 UTC
Further analysis shows that records are lost in the import process. Importing
gnr_part1 into Oo2.2 creates 40905 records. Importing into Excel creates 42511
records.
After a record-by-record comparison of the two files the first problem occurs at
the following record in Oo2.2:
#10309 9498 Bromiumbong Dam
Some 225  records are "missing" at this point. Further analysis shows that the
missing records are being imported into the columns of this row (#10309) until
Column IU (at the 255 column limit) is reached.
This problem is repeated a number of times throughout the Import, thereby
explaining the 1606 records missing.

Graham M 
Comment 3 frank 2007-07-10 14:25:47 UTC
Hi, 

this is a double to Issue 76874 and therefore a double to Issue 75199 .

Frank

*** This issue has been marked as a duplicate of 75199 ***
Comment 4 frank 2007-07-10 14:26:07 UTC
clcosed double
Comment 5 pagalmes.lists 2007-07-10 15:21:50 UTC
Are you sure it is a double from issue 75199?

The message "The maximum number of ROWS has been exceeded. Excess ROWS were not
imported." is displayed.

It is not related to COLUMNS, like issue 75199.
Comment 6 frank 2007-07-10 15:47:11 UTC
Yes I'm sure.
Have a look at desrciption 3 from gmichalk Thu Jun 14 08:17:36 +0000 2007 .
He found out that the columns are exceeded due to some uneven textdelimiters or
so, making some columns wider than others and therefore mixing up the data.

Frank

*** This issue has been marked as a duplicate of 75199 ***
Comment 7 frank 2007-07-10 15:47:54 UTC
closed double.

BTW comments can be added without reopening of Issues too.