Importing CSV file with more than 65535 rows to Excel 2007

D

d7666

Currently I am running Excel 2002. I am aware of the 65535 row limit
in this version.

Excel 2007 is stated in
http://office.microsoft.com/en-us/excel/HA100778231033.aspx
to have 1,048,576 rows.

My question is, if my raw data is a single CSV file of more than 65535
rows, can this be *directly* imported into Excel 2007 by <File> <Open>
<filename.csv> etc.?

Reason for question is I have seen questions concerning difficulty
with more rows than 65535 but most seem to be about xls files [old
versions] solved with xlsx [2007] files ... but is there a restriction
on CSV files *before* saving as xlsx ?

I don't have access to Excel 2007 to try this out ... but if it does
work I might buy it.
 
B

Bernard Liengme

The problems arise when Excel 2007 is running in compatibility mode - this
happens when you open an XLS file in Excel2007
I have just made a CSV with 12,000 rows. It opened just fine in XL2007 will
all rows present and accounted for
best wishes
 
C

CLR

I have occasion to extract data from ACCESS files containing more than 65000
rows, so I use MSQuery and filter the data to one sheet, and then run another
to filter more to another sheet, etc, eventually getting all the
rows......clumbsy but it works......maybe it would work with CSV files
too....don't know

Vaya con Dios,
Chuck, CABGx3
 
H

Homey

Text file with 1,048,576 rows opens ok for me in Excel 2007. slow though.


| The problems arise when Excel 2007 is running in compatibility mode - this
| happens when you open an XLS file in Excel2007
| I have just made a CSV with 12,000 rows. It opened just fine in XL2007
will
| all rows present and accounted for
| best wishes
| --
| Bernard V Liengme
| Microsoft Excel MVP
| http://people.stfx.ca/bliengme
| remove caps from email
|
| | > Currently I am running Excel 2002. I am aware of the 65535 row limit
| > in this version.
| >
| > Excel 2007 is stated in
| > http://office.microsoft.com/en-us/excel/HA100778231033.aspx
| > to have 1,048,576 rows.
| >
| > My question is, if my raw data is a single CSV file of more than 65535
| > rows, can this be *directly* imported into Excel 2007 by <File> <Open>
| > <filename.csv> etc.?
| >
| > Reason for question is I have seen questions concerning difficulty
| > with more rows than 65535 but most seem to be about xls files [old
| > versions] solved with xlsx [2007] files ... but is there a restriction
| > on CSV files *before* saving as xlsx ?
| >
| > I don't have access to Excel 2007 to try this out ... but if it does
| > work I might buy it.
| >
| >
| > --
| > Nick
|
|
 
D

d7666

The problems arise when Excel 2007 is running in compatibility mode - this
happens when you open an XLS file in Excel2007
I have just made a CSV with 12,000 rows. It opened just fine in XL2007 will
all rows present and accounted for
best wishes
--
Bernard V Liengme
Microsoft Excel MVPhttp://people.stfx.ca/bliengme
remove caps from email




Currently I am running Excel 2002. I am aware of the 65535 row limit
in this version.
My question is, if my raw data is a single CSV file of more than 65535
rows, can this be *directly* imported into Excel 2007 by <File> <Open>
<filename.csv> etc.?
Reason for question is I have seen questions concerning difficulty
with more rows than 65535 but most seem to be about xls files [old
versions] solved with xlsx [2007] files ... but is there a restriction
on CSV files *before* saving as xlsx ?
I don't have access to Excel 2007 to try this out ... but if it does
work I might buy it.

- Show quoted text -

Thanks for quick reply.
 
D

d7666

On May 12, 8:38 pm, (e-mail address removed) wrote:



In the mean time for an urgent work around I found in MS Knowledge
Base

http://support.microsoft.com/default.aspx?scid=kb;en-us;120596

that contains a macro for importing large row text files by splitting
the input into multiple worksheets. I have it tested and have it
running, and it does the urgent CSV file job I needed, and although
sucessful it does terminate with a debug error. While I've created
macros before, the script in this one is beyond my current skills, so
for now I've added a reply to the MS page with a feedback comment.
 
D

d7666

On May 12, 8:38 pm, (e-mail address removed) wrote:



In the mean time for an urgent work around I found in MS Knowledge
Base

http://support.microsoft.com/default.aspx?scid=kb;en-us;120596

that contains a macro for importing large row text files by splitting
the input into multiple worksheets. I have it tested and have it
running, and it does the urgent CSV file job I needed, and although
sucessful it does terminate with a debug error. While I've created
macros before, the script in this one is beyond my current skills, so
for now I've added a reply to the MS page with a feedback comment.
 
D

d7666

On May 12, 8:38 pm, (e-mail address removed) wrote:

In the mean time for an urgent work around I found in MS Knowledge
Base

http://support.microsoft.com/default.aspx?scid=kb;en-us;120596

that contains a macro for importing large row text files by splitting
the input into multiple worksheets.  I have it tested and have it
running, and it does the urgent CSV file job I needed, and although
sucessful it does terminate with a debug error. While I've created
macros before, the script in this one is beyond my current skills, so
for now I've added a reply to the MS page with a feedback comment.

A further test, I've found the debug error only arises if the input
files is *exactly* 65536 or exact multiples of 65536 lines long.
Works fine with other file lengths.
 
D

d7666

On May 12, 8:38 pm, (e-mail address removed) wrote:

In the mean time for an urgent work around I found in MS Knowledge
Base

http://support.microsoft.com/default.aspx?scid=kb;en-us;120596

that contains a macro for importing large row text files by splitting
the input into multiple worksheets.  I have it tested and have it
running, and it does the urgent CSV file job I needed, and although
sucessful it does terminate with a debug error. While I've created
macros before, the script in this one is beyond my current skills, so
for now I've added a reply to the MS page with a feedback comment.

A further test, I've found the debug error only arises if the input
files is *exactly* 65536 or exact multiples of 65536 lines long.
Works fine with other file lengths.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top