> > AFAIK , cf releases COM at the end of script execution. YOu
> > chould do
> >
> > <cfset myobj = nothing>
> > but I don't think there is any difference
>
> Unfortunately, it doesn't.
>
> We are finding that if we need to replace the COM object with
> a newer one, that CF is holding onto it.
>
> will nothing just like that work?
There are two different things going on here.
CF destroys the instantiated object at the end of a script. As far as I
know, trying to set the object's reference to "Nothing" doesn't actually do
anything in CF.
However, CF loads the COM object's DLL in memory, and this probably locks
the file, preventing you from releasing it. This is a different problem -
you can only cycle the service to release the file. This isn't specific to
CF, either. Other COM clients may do this as well.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
