Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Hi :)
I'm just wondering if Gnumeric might be better at opening the file?  

Calc 'should' be able to handle it easily so there is something weird there.  The file-size drop 
sounds like the old bug about images dropping out but we haven't seen that happen for around a year 
afaik.  Is it definitely an Xls and not an XlsX?  XlsX and Odt can be opened as though they were 
Zip files which allows you to poke around inside a lot more.  On the other hand Xls is usually a 
lot more stable than XlsX.  15Mb is pretty large for a normal file unless it does have images 
embedded inside.  

Could you just open LibreOffice itself, without opening the Xls, and go to 

Tools - Options - Memory

and bump up those figures a LOT.  Particularly the "Memory per object" to maybe around 15Mb, or 
something huge like that.  I'm assuming your Ram is over 1Gb and could handle it quite easily.  
Perhaps drop the number of undo steps it remembers to maybe 50.  Mine seems excessive at 100.  

I don't know why the file-size keeps changing.  It's something that would worry me so i would save 
as an Odt to make sure i got a stable copy and then possibly start exploring the Xls to see why 
it's so unstable.  Csv holds no formatting information so it's bound to be a lot smaller than an 
Xls or Odt.  It also strips out any images and macros and stuff.  

Regards from 
Tom :)  

From: Jay Lozier <>
Sent: Tuesday, 26 February 2013, 4:19
Subject: Re: [libreoffice-users] Problem loading and saving XLS files

On 02/25/2013 06:19 PM, Carl Paulsen wrote:
I'm using LO  on a Mac OS 10.6.8

I'm working on a critical project analyzing data from Salesforce (I'll call it SF) for 
non-profit SF users.  When I export xls files from SF, if those files are greater than something 
like 7,000 records (a dozen or so fields), the file gets truncated by LO.  The files (some with 
21,000+ records) open fine in MS Excel (on a PC at least - I don't own Excel on my Mac).

If I export from SF as .csv files, these open fine in LO and I can manipulate them fine.  Saving 
is also OK and I seem to be able to export to .xls, which then opens fine in LO with all 21000 

Any idea why the SF export of .xls file type won't open properly in LO?  What could cause this 
problem?  Could this be a bug in LO?  I realize there could be oddities in the SF export 
function, but given it opens fine in Excel (on a PC at least)

Note I can see something going on with the file size.  The .xls direct from SF is 15MB.  After 
opening this file and then saving it, the file size is 3-6MB (and it has only about 7000 
records). The .csv file that's exported from SF is about 2-3MB, but when I save the .csv file as 
.xls, the file is still only 3-4MB but it's complete (all 21000 records).


The problem is not the number of records since importing the csv file does not truncate. Most 
spreadsheets do have an upper limit for the number of records and for Excel and Calc I believe it 
is much larger than 21K.

Can you import the csv file and then save as an xls file and then reopen the xls file without data 

-- Jay Lozier

-- For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.