Word 2003 Shut Down error

[C Goebel]

When users shut down their machines at night they are getting a "W" shut down
error...looks like Word had not closed and asks you to click "End Now" to
stop the application.

We do merge documents from an SQL database. I am unsure if this might be
casueing the hang up on shut down?

-Catherine Goebel
Applications Specialist
Habush Habush & Rottier S.C.

 

[Beth Melton]

That could be the problem if it involves automation. A common error
developers make is they don't end the Word task correctly or their
code may create a second instance of Word and it remains in memory.

Have you tried not utilizing the merge functionality to see if the
same error occurs?

--
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

 

[C Goebel]

Thanks for the response Beth.....

I should be more clear about my situation:

I work for a law firm...our case information is in an ASA (Adaptive Server
Anywhere) SQL-based database.

It seems that when folks merge they get the shutdown error, and only after
they merge documents that day....they do not seem to get the error when they
do not merge documents.

Catherine Goebel
Applications Specialist
Habush Habush & Rottier S.C.

 

[Beth Melton]

That's the part I wasn't sure of. Thanks for the additional details.

So to confirm, they start the merge in Word rather than initiate the
merge from another application, such as a VB application?

If the latter then the developer needs to make some modifications. If
the former then can you provide the exact steps you are using? Also,
is Word 2003 patched to Office 2003 SP-1?

--
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

 

[C Goebel]

We do iniciate the merge from the database side....a speciliazed case
management program called Needles. The Needles application is database
driven, apparently with ASA/SQL "running in the background".

We are using Word 2003, most of us are on service pack two. I have had to
disable the built in Firewall that the new office Suite came with for other
functions, do you think this may be affecting the shutdown process?

-Catherine
Habush Habush & Rottier S.C.
(e-mail address removed)

 

[Beth Melton]

If you are initiating the merge from another application then therein
lies the problem. This the automation error I referred to in my first
reply. Whoever created the automation code didn't control the Word
instance correctly. Either they failed to quit the application
instance, or more commonly, didn't create their application object
correctly.

Unfortunately the error is in their code and there is little you can
do on the Word side. The only thing you can do is after you exit Word,
and Outlook if using Word as the email editor, display the Task
Manager and end any Winword.exe tasks that appear on the Processes
tab. I suspect you'll find an instance of Winword.exe running for each
time you initiate the merge so there could be several. :-(

--
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/