Tech Support Forum - View Single Post - Excel Hourglassing on File Open - can't seem to break

metallironi · 06-24-2009, 08:02 AM

Can someone help me break what appears to be an iterative loop of some sort that is keeping me from fully opening an Excel workbook? Ctrl+Break isn't working, despite my couple hundred attempts!

I have several hundred hours of work currently trapped in a file (no backup jokes please!) that won't let me break the hourglassing when I open it up. It shows me the tabs, the worksheets are intact, but I can't break whatever code is executing in the background.

Many macros (recorded and cleaned up, I'm not a VBA expert), and the last time I had it open to work in it, I was recording some macros that were giving me an error upon compiling, and I happened to notice that each macro was preceded by the file path (and I only had this particular file open at the time, which bewildered me because whenever I've only had only one file open before, excel has never preceded macro names with file paths, only the macro name was necessary)

This 'file path' phenomenon was true for all but two macros - one that was written by someone else to establish a connection between this worksheet and an AccessDB, and one that I couldn't see the actual name of...

06-24-2009, 08:02 AM	#1 (permalink)
metallironi Registered User Join Date: Jun 2009 Posts: 1 OS: Windows XP	Excel Hourglassing on File Open - can't seem to break - How to Interrupt Can someone help me break what appears to be an iterative loop of some sort that is keeping me from fully opening an Excel workbook? Ctrl+Break isn't working, despite my couple hundred attempts! I have several hundred hours of work currently trapped in a file (no backup jokes please!) that won't let me break the hourglassing when I open it up. It shows me the tabs, the worksheets are intact, but I can't break whatever code is executing in the background. Many macros (recorded and cleaned up, I'm not a VBA expert), and the last time I had it open to work in it, I was recording some macros that were giving me an error upon compiling, and I happened to notice that each macro was preceded by the file path (and I only had this particular file open at the time, which bewildered me because whenever I've only had only one file open before, excel has never preceded macro names with file paths, only the macro name was necessary) This 'file path' phenomenon was true for all but two macros - one that was written by someone else to establish a connection between this worksheet and an AccessDB, and one that I couldn't see the actual name of...