Excel locks up, then saves, then unlocks

I have a spreadsheet that is not very large. Randomly, when I am entering data, the program locks up for 30-45 seconds. I cannot do anything in Excel during this time---I cannot even close it. After this time passes, the "Save" icon appears in the status bar as if it is auto-saving. Once the icon disappears, the program and file is unlocked and I can continue. This series of events continues as long as I am using the file.

The lock-up does not affect any other part of my PC or any other programs.
I am using Windows XP and Excel 2003.

My company has uninstalled and reinstalled the Excel program and even given me a completely different computer, but no change. So I am thinking it must be something in the file. I am hoping it is something fixable and not a corrupt file.

Does anyone have any suggestions for a fix?

Thanks!

Hi Andi -- Two quick ideas to test and troubleshoot this:

1. Email the spreadsheet to a co-worker and see if the performance issue is present there

2. Also test other spreadsheets to see if performance issues are present there.

Based on what you've shared, I'm 99.4% sure there's an issue with the spreadsheet itself Sometimes, I've seen some inefficiencies in spreadsheets where folks highlight a row and set a color that goes all the way across. If you have macros, formulas, etc., that can slow down things. It may be trying to fetch data somewhere in an inefficient manner or is timing out doing so? Finally being in the security field, there are sometimes Macro viruses embedded, but that may not be an issue for you as your company PC should have AV protection.

If it's not complex with macros/calcuations you can highlight the X and Y boundaries, copy it to notepad and then paste it into another spreadsheet. If you have a friend at work that knows Excel really well they might be able to fix the issue

Good luck and I hope these issues are soon solved for you

I just realized I never said thank you for your post, which was a very very long time ago. My company ended up rebuilding my PC to solve the problem, the cause of which has remained a mystery. Thank you for the ideas you gave me - I am keeping them in mind in case I have that problem happen again!