>
> <CFTRY>
> <!--- If it exists, connect to it --->
> <br>Trying to connect to Word Object
> <CFOBJECT
> ACTION=""> > CLASS="Word.Application"
> NAME="oWord"
> TYPE="COM">
> <CFCATCH>
> <!--- The object doesn't exist, so create it --->
> <br>Word Object not found, trying to create one
> <CFOBJECT
> ACTION=""> > CLASS="Word.Application"
> NAME="oWord"
> TYPE="COM">
> </CFCATCH>
> </CFTRY>
>
> I don't see the catch section running, so I'm apparently
> connecting to an existing instance of a Word Object.
> However, I am getting a new WINWORD.EXE process running
> whenever I run this code. The moment I have a second
> instance (or more), my processing begins to bog down badly.
>
> Is there any way to prevent this situation?
Are you closing off the COM object once you've finished your work?
If not, then you're leaving the connection active, which can sap
resources badly
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
