shared workbook woes

  • Thread starter Thread starter Troy Shatz
  • Start date Start date
T

Troy Shatz

Hi All,

We have a shared workbook hosted on a win2K box that crashes regularly
especially for Citrix users.

The workbook has a number of sheets however users would predominatly
be working on the same sheet within the book.

Users attempt to save the file but the excel 'process' simply bombs
out and no longer appears in task manager.

Usually a 8 character temp file is created.

Admittedly this book has evolved over the years with the company and a
'proper' DB would be more suitable however these crashes can occur
with very few users (2 or less).

To prevent crashes we've removed write access to file bar one PC
user.

Whilst the DB is being developed I'm looking to improve matters,
Crashes are still noted if users are given write access but propted
for read only and educated on shared workbook 'best practices'.

I'm aware the multiuser enviroment isn't suited to excel (2000 for
most users) however IMHO the workbook crashes *way* more than it
should.

Looking on the server using computer management to see the state of
the file I see that shared workbooks aren't listed as open files can
anyone confirm that this is 'usua'l?

If anyone out there has any tips /tricks for improving matters or
suggestions for avenues I could explore I'd really love to hear them.

Cheers Guys,
T
 
Have you tried removing the shared workbook tick and then opening and closing
the workbook. That does seem to clean thing up a bit. I once had a shared
workbook grow to 80MB and after removing the sharing and opening and closing it
once or twice it dropped back to 1MB or so.
 
Have you tried removing the shared workbook tick and then opening and closing
the workbook. That does seem to clean thing up a bit. I once had a shared
workbook grow to 80MB and after removing the sharing and opening and closing it
once or twice it dropped back to 1MB or so.
Click to expand...

Hi Dave,

Yes, tried that and a complete new workbook, it does bring it back
down in size but we shouldn't have to do this on a daily basis.

It's really the frequency of crashes I'm attempting to limit and I'm
not making much headway.

Cheers anyways,

T
 
Back
Top