I'm sure there are those much more in touch with Excel than I who will weigh
in with more valuable opinions, Chuck. But my first guess is that your code
connects with some other process or application that causes a conflict. I
had a problem with certain macros in Word before I realized it was
conflicting with my Outlook, which used Word as editor but a different
template. Have you stepped through everything watching the Immediate and
Locals windows?

Another possibility is that your code may activate a process in another
workbook/document/application, and may want to move on before that process
is accomplished. If I create a workbook and hand it to you to file away,
then rush off to use that workbook before you've finished your task, I'm
going to crash. Or if your code grabs data from another file, then tries to
act on it before the data is copied or the source file deactivated or
whatever, you could have a problem. I crashed one macro several times until
I realized I hadn't changed the focus back to my wkbk1; if wkbk2 wasn't
completely closed and gone by the time that line of code hit, I got this
pretty little message box with an exclamation point. If it's the e-mail
bit, or any other over-the-network process, your problem may have more to do
with your code outrunning your network speed.

That's about tapped out my thoughts for the day. I wish you luck.
Ed

"Chuck Buchanan" wrote in message
...
Ed, thanks ... here are some answers to your pertinent questions:

(a) Is this workbook stand-alone on a machine? Or on a network? Shared?

STANDALONE

(b) When it "gronks", is it always/never/usually when it is opened for
the
first time that day? When it is opened when another application is open?

ALL OF THE ABOVE ... TOTALLY RANDOM

(c) "Loaded with VBA code" - does the code reach out and touch any other
files or applications? If so, are the "gronks" after you've run some
code?

VBA CODE EVENTUALLY READS SOME .TXT FILES, BUT EXCEL DIES BEFORE HITTING
THAT MOD

(d) Can we assume the file did not appear full-blown with code and
UserForm - that is, it was built up a piece at the time, and worked just
fine, until ...? Until what? What was changed? added? deleted? Was it
done by someone else who might not have been familiar with all the code?

YEAH, IT WAS A 2-MAN EFFORT OVER SEVERAL MONTHS ... FIRST NOTICED AROUND
THE TIME WE HAD IT FIRE-OFF AN OUTLOOK EMAIL

(e) Do you get an error message at "gronk" that you would care to share?

OFFICE 2003 AND/OR XP SPITS OUT A VOLUMINOUS ERROR LOG, BUT NO "ERROR 95"
STYLE MESSAGE

(f) Have you ever checked the Task Manager before opening to make sure
there are no extraneous or questionable processes? After "gronk", have
you
ever had to use the TM to end Excel? Or any other app that was touched by
your code?

NEVER CHECKED TM (BUT WILL) ...