Wow! Thanks, Jezebel. I owe you big for that one! I guess I need to go
back and brush up on some things - and see what other bad habits I've let
get in here.

Ed

"Jezebel" wrote in message
...
Not sure that this is entirely the cause of the problem, but your object
declaration and instantation are screwy. You're using early binding for
the declaration itself, but using late binding for the instantiation; and
using 'as new' in the declaration is a recipe for disaster. (Some coding
shops have an absolute ban on the use of 'as new'.) As it is, this
statement

Set appWD = CreateObject("Word.Application")

will instantiate TWO copies of Word: one created automatically for the
first use of appWD, and one from the CreateObject statement.

Try ---

Dim appWD as Word.Application

on error resume next
set appWD = Word.Application 'Get existing instance if any
on error goto ErrorHandler

if appWD is nothing then 'No existing instance,
so create a new one
set appWD = new Word.Application
end if



Two other issues that might be relevant --

1) Word may refuse to close if there were unhandled errors in the course
of your code.
2) There may be other code, from normal.dot or an add-in, that is
interfering.

After you've run your macro, check the Task Manager to see if there are
any remaining instances of Word.







"Ed" wrote in message
...
Thanks for the response, Jim, and sorry for the confusion. The objects
are declared with:
Dim appWD As New Word.Application
Dim doc As Word.Document
and set with:
Set appWD = CreateObject("Word.Application")
appWD.Visible = False
Set doc = appWD.Documents.Add

My assumption was that Excel VBA would thereafter recognize "doc" as
having Word properties and methods, so
doc.Close SaveChanges:=wdDoNotSaveChanges
should be recognized. Is this an inaccurate assumption?

Ed

"Jim Cone" wrote in message
...
Ed,

There are a couple of things that could be confusing to the
applications...

How would Word or Excel read: appWD.doc.Close...?
Is appWD the document or is doc the document?
Maybe doc is not the best choice for a Word object variable.

Since wdDoNotSaveChanges is not an Excel constant and you are
running the program from Excel, you should qualify the constant...
appWD.wdDoNotSaveChanges
--
Jim Cone
San Francisco, USA
http://www.realezsites.com/bus/primitivesoftware



"Ed" wrote in message
...
I have an Excel macro that call a new instance of Word and creates a new
document, does some things in the doc, then closes the doc without
saving
changes and sets the doc and Word app objects to nothing using
doc.Close SaveChanges:=wdDoNotSaveChanges
appWD.Quit
Set doc = Nothing
Set appWD = Nothing

I used the macro this morning repeatedly - perhaps 30 times in
succession.
(Each time had to be an individual call - there was no way to loop
this.)
After doing all that, I did not check to see if there were any open
instances of Word left (there were none during testing, so I didn't
think I
should have to) or other issues. Then I tried to open a Word document
with
an AutoOpen macro, and Word crashed. Subsequent attempts produced
further
crashes. I wound up eventually having to rebuild Normal to get things
moving again.

Question: Could just repeatedly accessing the Word app have caused
this?
Is there a better way to avoid these issues in the future?

Ed