Does anyone know why - when you save your Excel workbook -it sometimes
says it has close, sorry for the inconvienience and
you lose hours of work and/or data entry? It really ****es me off
and has happened twice in the last 2 days !

The Save and recover option (if that's what it is) hasn't helped. I've
not managed to rescue anything. What does it intend at this point ?
Whatever you do isn't want you want and you lose the workbook a second
time!

Why can't it just bloody SAVE the file first, then crash? That way
you wouldn't lose anything.

My xls is rather large, 37 megs. Is that perhaps a factor? I don't
want to use auto save as that takes ages and is very intrusive.

Cheers - Kirk

Hi Kirk,

I understand your anger and frustration!

If you mean you loose hours of work, is it because hours have passed since
the last save, or is it that the file gets corrupted?

If the first, then the solution is simple.

If the second, it really depends on the available memory on your PC. Excel
limitations are expressed in number of rows, columns, cells and such, but not
in file size.


--
HTH

Kassie

Replace xxx with hotmail


"kirkm" wrote:

Does anyone know why - when you save your Excel workbook -it sometimes
says it has close, sorry for the inconvienience and
you lose hours of work and/or data entry? It really ****es me off
and has happened twice in the last 2 days !

The Save and recover option (if that's what it is) hasn't helped. I've
not managed to rescue anything. What does it intend at this point ?
Whatever you do isn't want you want and you lose the workbook a second
time!

Why can't it just bloody SAVE the file first, then crash? That way
you wouldn't lose anything.

My xls is rather large, 37 megs. Is that perhaps a factor? I don't
want to use auto save as that takes ages and is very intrusive.

Cheers - Kirk

On Thu, 9 Apr 2009 08:19:03 -0700, Kassie
wrote:

Hi Kirk,

I understand your anger and frustration!

Thanks Kassie.... it's nt fun doing 8 hours of OCR, cleaning the data,
writing it all to a new sheet.... then losing the lot ! TWICE !!

If you mean you loose hours of work, is it because hours have passed since
the last save, or is it that the file gets corrupted?

I believe it's the former... it's when I save the problem arises. If
there is corruption I guess it goes with the lost file.

When Excel falls over, it offers to save /recover. To you know the
steps to get at this reocovered file ?

If the first, then the solution is simple.

If the second, it really depends on the available memory on your PC. Excel
limitations are expressed in number of rows, columns, cells and such, but not
in file size.

I have 2GB of RAM. Nothing else seems to suffer. I reload Excel and
away again till the next time.


Cheers - Kirk

Two things here.
Firstly, when your workbook is that big you are probably better off with
storing the data
away from Excel, maybe in a database such as SQLite.
Secondly, you need to clean your code from time to time with a code cleaner:
http://www.appspro.com/Utilities/CodeCleaner.htm

RBS


<kirkm wrote in message ...
Does anyone know why - when you save your Excel workbook -it sometimes
says it has close, sorry for the inconvienience and
you lose hours of work and/or data entry? It really ****es me off
and has happened twice in the last 2 days !

The Save and recover option (if that's what it is) hasn't helped. I've
not managed to rescue anything. What does it intend at this point ?
Whatever you do isn't want you want and you lose the workbook a second
time!

Why can't it just bloody SAVE the file first, then crash? That way
you wouldn't lose anything.

My xls is rather large, 37 megs. Is that perhaps a factor? I don't
want to use auto save as that takes ages and is very intrusive.

Cheers - Kirk

On Thu, 9 Apr 2009 20:30:24 +0100, "RB Smissaert"
wrote:

Two things here.
Firstly, when your workbook is that big you are probably better off with
storing the data
away from Excel, maybe in a database such as SQLite.
Secondly, you need to clean your code from time to time with a code cleaner:
http://www.appspro.com/Utilities/CodeCleaner.htm

RBS

I'll try that and thanks for the tip. Yes I have much redundant code,
some of it temporary which I don't delete, in case it's wanted again.
But the problem arises when I save the xls, not when (my) code is
executing.
Would rather not have a seperate front/back end, but if that's what
is causing the crashes....

Cheers - Kirk