VBA editor get confused, crashes and hangs frequently

[Jerry Natowitz]

I have noticed that it is very easy to get the VBA editor to get
confused. One way is to delete or change the name of a subroutine. One
of three things will happen:

1) An immediate crash - I send these on occasionally to Microsoft, does
any really look at them?

2) Persistent syntax errors about having code past an "End Sub". This
is the most serious, as I can no longer use the spreadsheet. When I use
the Object browser it shows a subroutine that no longer exists.

3) "Whirling circle of death", as a coworker calls it. I have to issue
a kill -1 <PID> to be able to recover.

 

[JE McGimpsey]

I have noticed that it is very easy to get the VBA editor to get
confused. One way is to delete or change the name of a subroutine. One
of three things will happen:

1) An immediate crash - I send these on occasionally to Microsoft, does
any really look at them?

Crash reports are read by MacBU - though it appears they're aggregated
first.

2) Persistent syntax errors about having code past an "End Sub". This
is the most serious, as I can no longer use the spreadsheet. When I use
the Object browser it shows a subroutine that no longer exists.

I've seen this a few times. I copy the remaining code to a new module,
delete the old one, and close and reopen the file.

3) "Whirling circle of death", as a coworker calls it. I have to issue
a kill -1 <PID> to be able to recover.

Haven't seen this myself. Can you replicate this consistently?

If you have additional details, let me know - I'm compiling a list of
bugs that I've found:

http://www.mcgimpsey.com/macoffice/excel/04/xl04bugs.html

 

[Jim Gordon MVP]

Hi Jerry,

I was experiencing similar behavior. After I ran TechTools Deluxe and had it
repair the volume information (it took a long long time) and used Disk
Utility to Repair Permissions the problem went away.

Perhaps your OS needs a tune up.

-Jim

--
Jim Gordon
Mac MVP

MVPs are not Microsoft Employees
MVP info

 

[Jerry Natowitz]

Hi Jim,

I just tried that, and it didn't help. In fact, after trying to delete
a subroutine, I am now the owner of a Workbook that crashes upon
opening. Fortunately, I take frequent snapshots of the Workbook, so I'm
not up the proverbial creek - this time.

Am I missing some technique that is supposed to be used to delete routines?

Jerry

 

[Jim Gordon MVP]

Hi again Jerry,

if it is just one workbook in particular that's causing fits, copy the text
from the vba editor into a plain text editor so that there's no chance of
hidden characters or control characters being used. Then, as John described,
Delete all the modules from the troubled workbook. Save the workbook with a
new file name then close it. Open the workbook and make new modules and
paste in the text from the old modules.

-Jim Gordon
Mac MVP

All responses should be made to this newsgroup within the same thread.
Thanks.

About Microsoft MVPs:
http://www.mvps.org/

Before posting a "new" topic please be sure to search Google Groups to see
if your question has already been answered.


----------