The project file " is corrupt and can't be opened

Excel 97 SR2 on Win98 SE.

I run into this error message periodically. This doesn't occur on any
particular file(s). If it happens when I open the file manually, it's
really just a nuisance. Dismissing the MessageBox a few times will
overcome the problem most of the time.

However, when I am running routines using the OnTime method (about
eight hours worth), it really gums up the works, because everything
grinds to a halt.

Is there any way to trap this error?

Many TIA

Paul

This "event" is not a feature. It's a problem with your workbook. If it were
happening to me, I think I would be spending some time recreating that
workbook--someday, you may not be able to even open that workbook (or maybe
it'll just stay the way it is???).

Anyway...

Lots of people have praised OpenOffice.org for saving their data and code.
Maybe it'll save some of your images.

http://www.openoffice.org, a 60-65 meg download or a CD

There are commercial recovery services. I've never used it, but you might want
to check into:
http://www.officerecovery.com

And sometimes newer versions of excel can open files that older versions can't.
(And sometimes just different versions may work, too!)

am wrote:

The project file " is corrupt and can't be opened

Excel 97 SR2 on Win98 SE.

I run into this error message periodically. This doesn't occur on any
particular file(s). If it happens when I open the file manually, it's
really just a nuisance. Dismissing the MessageBox a few times will
overcome the problem most of the time.

However, when I am running routines using the OnTime method (about
eight hours worth), it really gums up the works, because everything
grinds to a halt.

Is there any way to trap this error?

Many TIA

Paul

--

Dave Peterson

Dave,

Thanks for the prompt and informative response. Unfortunately (or
fortunately, depending on your perspective) this error happens
sporadically on different workbooks. If it were just a junked
workbook, I have a set of routines that I wrote that would recreate
the workbook fairly effectively.

When it happens once, it tends to repeat on different workbooks. I've
never had to recreate a workbook based on this error, and I have
records of this problem's occurrence going back to 2001. Shutting down
and restarting Excel helps.

I have routines that download stock market data from various WebSites
over a period of 6.5 hours (on average every five minutes). Then, for
an hour or so (after the market closes), I have routines that are
downloading and processing data If I'm sitting at the computer and it
happens, no big deal. Click and go. If not, then Excel stops, and
......

Last time, I encountered this problem was six months ago. This past
week, it happened twice. I was out and about for three hours on one
instance, and lost about two hours of downloading.

After searching through Google a half dozen times over the past 2-3
years, I've never been able to find anyone who provided a way to trap
this error.

Thanks
Paul


wrote:

This "event" is not a feature. It's a problem with your workbook. If it were
happening to me, I think I would be spending some time recreating that
workbook--someday, you may not be able to even open that workbook (or maybe
it'll just stay the way it is???).

Anyway...

Lots of people have praised OpenOffice.org for saving their data and code.
Maybe it'll save some of your images.

http://www.openoffice.org, a 60-65 meg download or a CD

There are commercial recovery services. I've never used it, but you might want
to check into:
http://www.officerecovery.com

And sometimes newer versions of excel can open files that older versions can't.
(And sometimes just different versions may work, too!)

wrote:

The project file " is corrupt and can't be opened

Excel 97 SR2 on Win98 SE.

I run into this error message periodically. This doesn't occur on any
particular file(s). If it happens when I open the file manually, it's
really just a nuisance. Dismissing the MessageBox a few times will
overcome the problem most of the time.

However, when I am running routines using the OnTime method (about
eight hours worth), it really gums up the works, because everything
grinds to a halt.

Is there any way to trap this error?

Many TIA

Paul

It's not a trappable event.

There is no workbook_beforeblowup() event <bg.

I'd still put my money on a corrupted workbook--well, some stage of corruption.

You might get lucky by just opening in OpenOffice and saving there--but I'd do
it against a copy of the original, just in case.

Good luck,



am wrote:

Dave,

Thanks for the prompt and informative response. Unfortunately (or
fortunately, depending on your perspective) this error happens
sporadically on different workbooks. If it were just a junked
workbook, I have a set of routines that I wrote that would recreate
the workbook fairly effectively.

When it happens once, it tends to repeat on different workbooks. I've
never had to recreate a workbook based on this error, and I have
records of this problem's occurrence going back to 2001. Shutting down
and restarting Excel helps.

I have routines that download stock market data from various WebSites
over a period of 6.5 hours (on average every five minutes). Then, for
an hour or so (after the market closes), I have routines that are
downloading and processing data If I'm sitting at the computer and it
happens, no big deal. Click and go. If not, then Excel stops, and
.....

Last time, I encountered this problem was six months ago. This past
week, it happened twice. I was out and about for three hours on one
instance, and lost about two hours of downloading.

After searching through Google a half dozen times over the past 2-3
years, I've never been able to find anyone who provided a way to trap
this error.

Thanks
Paul

wrote:

This "event" is not a feature. It's a problem with your workbook. If it were
happening to me, I think I would be spending some time recreating that
workbook--someday, you may not be able to even open that workbook (or maybe
it'll just stay the way it is???).

Anyway...

Lots of people have praised OpenOffice.org for saving their data and code.
Maybe it'll save some of your images.

http://www.openoffice.org, a 60-65 meg download or a CD

There are commercial recovery services. I've never used it, but you might want
to check into:
http://www.officerecovery.com

And sometimes newer versions of excel can open files that older versions can't.
(And sometimes just different versions may work, too!)

wrote:

The project file " is corrupt and can't be opened

Excel 97 SR2 on Win98 SE.

I run into this error message periodically. This doesn't occur on any
particular file(s). If it happens when I open the file manually, it's
really just a nuisance. Dismissing the MessageBox a few times will
overcome the problem most of the time.

However, when I am running routines using the OnTime method (about
eight hours worth), it really gums up the works, because everything
grinds to a halt.

Is there any way to trap this error?

Many TIA

Paul

--

Dave Peterson

Dave,

I don't know why you're referring to this as an "event". I know what
events are and how they handled. I haven't referred to this as an
"event".

It's an "error" message that is popping up. I'm looking to trap the
"error". This "error" has popped up intermittently on different
workbooks over the course of five years. ( I keep a log file on Excel
problems, crashes, etc) I've never recreated any of these workbooks
after this "error" message popped up. And I haven't had any problems
with these workbooks after this "error" message appeared (most contain
only data).

I could find nothing in "Trappable Errors" in VBE Help for this
particular issue. And my searches using Google for others who have had
the same problem have not provided a solution.

I have obviously had to deal often enough with other junked workbooks,
or I wouldn't have bothered to write a series of routines for
recreating workbooks that were corrupted by Excel.

I'll probably try to repost this during the week when there are more
eyes viewing the newsgroup in case other persons who have investigated
this issue have found a solution.

Thanks again.

Paul

--------------------------------------------------------------------------------

It's not a trappable event.

There is no workbook_beforeblowup() event <bg.

I'd still put my money on a corrupted workbook--well, some stage of corruption.

You might get lucky by just opening in OpenOffice and saving there--but I'd do
it against a copy of the original, just in case.

Good luck,

good luck.

am wrote:

Dave,

I don't know why you're referring to this as an "event". I know what
events are and how they handled. I haven't referred to this as an
"event".

It's an "error" message that is popping up. I'm looking to trap the
"error". This "error" has popped up intermittently on different
workbooks over the course of five years. ( I keep a log file on Excel
problems, crashes, etc) I've never recreated any of these workbooks
after this "error" message popped up. And I haven't had any problems
with these workbooks after this "error" message appeared (most contain
only data).

I could find nothing in "Trappable Errors" in VBE Help for this
particular issue. And my searches using Google for others who have had
the same problem have not provided a solution.

I have obviously had to deal often enough with other junked workbooks,
or I wouldn't have bothered to write a series of routines for
recreating workbooks that were corrupted by Excel.

I'll probably try to repost this during the week when there are more
eyes viewing the newsgroup in case other persons who have investigated
this issue have found a solution.

Thanks again.

Paul

--------------------------------------------------------------------------------

It's not a trappable event.

There is no workbook_beforeblowup() event <bg.

I'd still put my money on a corrupted workbook--well, some stage of corruption.

You might get lucky by just opening in OpenOffice and saving there--but I'd do
it against a copy of the original, just in case.

Good luck,

--

Dave Peterson

G'day there Paul

I'll probably try to repost this during the week when there are more
eyes viewing the newsgroup in case other persons who have investigated
this issue have found a solution.

It may well be unrelated, but I found a similar issue in one of my
projects with Excel 10 under XP Home. I found that if I simply opened
the workbook and didn't allow macros to run (I disabled them from the
startup dialogue), I could prevent the "Corrupt file" message on the
next start by going to the VBE & manually compiling the code and saving
without any alterations.

I don't know how or why it worked, but by doing the above actions
& then allowing macros the next time I was able to step through the code
& find the problem. You'd have to disable autostarting procedures if you
have any, but that's what worked for me.

Hope this helps
Ken McLennan
Qld, Australia