Excel Spreadsheets seem to be too large in size

[chriss...@hotmail.com]

Hello,

We have a problem here at the moment where some of our spreadsheets seem
to be far too large in relation to what they contain. We have tried to
educate users to save large spreadsheets out of GW DMS and directly onto
the server. This is because from what I have seen GW doesn't handle large
documents very well. The spreadsheet I am having problems with at the
moment is currently 70MB in size. It does contain formulae and a fair bit
of data, but I wouldn't expect it to be this size, more like 20MB max. I
have virus scanned it, no viruses were found. We currently are using
WinXP SP1, Office XP SP2, GW554. Has anyone experienced these problems
before or have an ideas how I can sort them out????

cheers

[Dave Parkes]

To chriss...@hotmail.com

Graphs are good for soaking up space, any in there ?

Cheers Dave

--

Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/

[chriss...@hotmail.com]

No mate, no graphs in there. If you try and open it from within GW we get
a message stating the pc's running out of virtual memory and it won't open
(or it probably will but takes ages). I've saved the file to the local
hard drive and this time it'll open without the virtual memory error, but
it takes longer than I would have thought it should. My plan was to copy
the worksheets one by one into a new spreadsheet, as we've had a similar
problem before and that fixed it, and reduced the file size dramatically.
However if I try and copy one worksheet I get an error stating there are
not enough resources. I'm guessing that the file is corrupt, but I'd like
to figure out what is causing the corruption and I'd like to get the data
out of the file so we don't lose it. I've been through the DMS trying to
restore an older version of the file stored in blob format before anyone
asks.

cheers

[Dave Parkes]

To chriss...@hotmail.com

Yep, sounds like the file itself is broken, Copying to a new file seems
your best/only bet.

[t...@hartfordinc.com]

This is a little related to your problem, but not specifically. I had a
problem with Excel spreadsheets 26Mb in size. Specifically, I was having
trouble saving them (time outs) sometimes. The problem came down to the
size of the spreadsheet, and the server it was on. In our case, we were
able to reduce the size of the spreadsheet to solve the problem. There are
docs out there from Microsoft and others than point to a problem saving to
a server vs a workstation for Excel. In our case, it was taking 45 seconds
to 1.5 minutes to save. One document I remember suggested saving to the
workstation (much faster), and then copying the file to the server as this
could speed up the process. There was even a macro I found to do this
automatically. I tried it, but it didn't save much time. The difference
for use really came when we switched servers. The old one was a Maxtor
NAS4300 running Windows 2000 for an operating system. Several documents
and support people pointed out that a server with a UNIX based operating
system would provide much faster throughput when opening/saving files. We
bought a Quantum Guardian 4400 (480GB Raid 5, Unix based OS). Our
open/save time dropped to about 7 seconds which was a vast improvement
over 45 seconds to 1.5 minutes. I cannot speak towards the Groupwise
aspect as I am just getting started in libraries and the DMS. Also, you
might want to take a look at what the processor speed and memory are at
the workstation if you're opening files of that size. That will make a
difference. We also saw a marked improvement when we upgraded one station
(key user) to gigabit Ethernet. That's all I got. Hope it helps.

[Phil Halbasch]

as far as the network opening and getting an error this is straight from the
man

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

found this after experiencing the problem with a user.