Try this instead.
<cftry>
<cfobject type="COM" name="server.interkomobject"
action="create">
<cfcatch>
<cfobject type="COM" name="server.interkomobject"
action="connect">
</cfcatch>
</cftry>
I think there is a better example in Ben's books.
-----Original Message-----
From: Franke, Ir. G.J. [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 7 February 2002 3:53 AM
To: CF-Talk
Subject: RE: Bug in CF 5.0 communicating with COM objects
>
> I've called COM Object procedures that take as long as 10 seconds to
> run
> from CFAS 5 with no errors. I hazard to guess the problem
> lies in your
> COM
> Object, the way in which you're calling the COM Object,your server
> configuration, or somewhere else.
>
> ~Simon
>
this is what happens:
application.cfm:
<cflock timeout="20" throwontimeout="yes" name="activeXinterface"
type="EXCLUSIVE">
<cfif not isdefined("server.interkomobject")>
<cfobject type="COM" name="server.interkomobject"
class="InterKOMConnector.IKConnector" action="create" context="LOCAL">
</cfif>
</cflock>
getinfo.cfm:
<cflock timeout="20" throwontimeout="yes" name="activeXinterface"
type="EXCLUSIVE">
<cfset session.connectorresult=
server.interkomobject.processandparserequests(session.cmdstring)>
</cflock>
______________________________________________________________________
Get Your Own Dedicated Windows 2000 Server
PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
Instant Activation � $99/Month � Free Setup
http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
