Hi Rick,
This sounds like a good reason to keep a backup. I make backup copies
daily of the application I'm developing.
Dan
On Sep 26, 1:25 pm, rleav...@smithgroupre.com wrote:
> Thanks for the reply. If I run this tool after trying to open the
> spreadsheet, it cancels out of Excel and gives me the option of
> "recovering" the original sheet. Since this is the one that is
> corrupted it does not do me any any good. Perhaps if I had run this
> when the sheet crashed originally I would be in better shape, but alas
> I did not. I have had this sort of thing occur before with large
> complicated sheets, and so I think there may be some bug in the auto-
> recovery function.
>
> Whatever, I don't really need to solve that, I was just hoping I could
> get my VB code out of the corrupted application.
> ...Rick
>
> On Sep 26, 2:54 pm, Joel <J...@discussions.microsoft.com> wrote:
>
> > Did you try Microsoft Office Recovery?
>
> > Start Menu - Programs - Microsoft Office - Tools - Microsoft Office
> > Application Recovery.
>
> > "rleav...@smithgroupre.com" wrote:
> > > I have a very large sheet (115M) that I cannot open for some reason
> > > (Excel hangs when I try to open). I can live with out the contents of
> > > the sheet, but would love to be able to get at the VBA that is
> > > contained within modules within the spreadsheet. In fact, I am
> > > desparate, Does anyone have any ideas for how to access this code
> > > without opening the sheet?
>
> > > I don't really know why the sheet won't open... but it has something
> > > to do with changes Excel made to the sheet during autorecovery
> > > operation.
>
> > > I am using Excel 2003 in XP-Pro
>
> > > Thanks,
> > > Rick- Hide quoted text -
>
> > - Show quoted text -
|