Did that, I do get the catch block running, but the winword.exe instance
isn't killed.


I have found another suitable method - save my templates as HTML, read in
the file, modify it as needed, then push it out as a word document.  No need
of Word automation with this method.  Will just have to train the users in
this slight difference.


Thanks anyways.


Shawn

-----Original Message-----
From: Philip Arnold [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 1:58 PM
To: CF-Talk
Subject: RE: Creating a Word.Application COM object needs a new instance o f
WI NWORD.EXE?

> Well, the server has been restarted, and the "Quit" command
> does indeed clean up the instance.  However, if I run into
> any errors at all before the Quit command (and I'm expecting
> a few while I'm developing the page), I run into the same
> situation again - the instance of word is not cleaned up, I
> cannot remove it, and a new instance is created when the page
> is loaded again.
>
> I'm sure someone has created word documents on the fly using
> the office automation tools before (server-side that is), so
> can someone point me to a resource that would help me through
> this process?  Thanks.

Put your processing code into a <CFTRY>, then below it, run the quit()

That way if your code breaks, it'll still end the process, and with some
intelligent coding, you can still see the error generated.
  _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to