I am consistently receiving what appears to be a significant Excel error on loading a spreadsheet that contains a large number of macros.

The error message asks me if I want to send the error log to Microsoft which I have tried but with no response.

The error is .... The instruction at "0x6007028d" referenced memory @ "0x00000000". The memory could not be read.

When I show the repairs I get
         Lost Visual Basic project
         Lost ActiveX controls.

Interestingly this error only occurs every other time that I open the spreadsheet.

Has anybody else come across this and if so are they aware of what is causing it and how to solve it.

Thanks

Frank

OK, for starters, the 'Send Log' bit is just so billg and friends know that something broke on someones machine - no way are they going to come back to you personally with a fix.

Now, the error message you're experiencing can mean that the spreadsheet itself is starting to get corrupted. In my experience, the best thing to now is:
get it open - without executing any on_open macros (hold down the shift key while selecting the file in the 'file open' menu) ;
save out all the macro code - 'export file' from the code editor;
create a new workbook and copy/paste all you worksheet formulae etc.
Once you have all your valuable code and data saved somewhere safe, you can start to experiment with the original file. I had a file go bad due to a group of three cells being corrupted - delete those cells and everything went back to normal! It might also be a bad link to an external dll - check the error message for the actual calling module (e.g. excel.exe, msador15.dll etc), that might give you a clue.

Best of Luck

Chris


There are two secrets to success in this world:
1. Never tell everything you know

Frank,

What you've (probably) got is a corrupted file. Why it happens is a slightly random affair which can be caused by files being too large, declaring variables sloppily or just plain bad luck.

You seem to be in some sort of luck though because you can open the file every other time. I would recomend that you copy all of the macro code out of the project into notepad (or some sort of plain text storage), then delete all of the modules and re-copy the code back into newly created modules in the same workbook. There is a utility out on the internet by someone called Rob Bovey (CodeCleaner, I think), which basically automates this process. If this dosen't work I would try doing the same but with a completely new workbook.

If it gets to the point whereby you can't open the file at all you are basically stuffed in terms of getting your code back (unless you've back-ups). However, you may be able to retrieve information contained on the sheets by using external linking.

Maccas

We´ve had the same problem in the company that I work in. When I try to open an excel file, generates excel the "memory could not be read" error and shutsdown.

The thing I've discovered is that when I first start a new blank excel file and then try to open the file I want to be opened, everything goes just the way it's supposed to... And another thing I've found out is that when I plug the computer off the company's network and then try to open the file I want to, everything works just fine.

The funny thing is that half of our 150 computers generate these errors and the other half works OK. Eventhough all the computers are the same...

Now we've handled the problem so that we've made the excel start automatically in startup. But I'd still like to know a better way to clear this problem... So, please someone help me!!

Save it in your desktop. Excel can open it faster and with ease if it's in your desktop no matter how big the file is. This problem occurs not only because its a huge file but also because it's in the share drive. If your the owner of the file save it in your desktop and update the file in the share drive.

Goodluck

We have a large workbook template that is used by 100 people in the company. 1 out of every 20 or reports that it has lost its VB project (Lost VB Project, Lost ActiveX Controls) when the workbook is reopened. It sounds like the same problem described earlier but we're trying to acertain why it happens to some and not to others when everyone is using the same template (it is stored on a network share). If it is corrupt cells or a bad link to an external .dll file, wouldn’t we see it more often? If it is corrupt cells, how can you identify them? Any suggestions would be appreciated.

Thanks.

Try tips from this page http://www.fdrlab.com/tips.html

Dave Hall
FDRLab Data Recovery Centre Consultant
http://www.fdrlab.com/


FDRLab Data Recovery Centre Consultant
http://www.fdrlab.com/