ActiveX container leaves temp files

[Mark T.]

We are using the ActiveX container in LabVIew to use a custom ActiveX
control. We have discovered that every time we run the LabVIew application
another temporary file is generated in the temp directory. In fact all we
have to do is open the VI that has the ActiveX container in it and a
temporary file is generated. These temporary files are never deleted
(unless we delete them manually). I though it may be our ActiveX control,
however we have tried multiple other ActiveX controls in several different
VI's and we get the same results, even when we use the National Instruments
CW controls. In all cases the VI does not need to run, just opening the VI
in LabVIew causes the temp file to be generated and never removed.


Does anyone know why this is happening or if there is a way to avoid this.
It is unacceptable to load up a customers machine with temporary files.

Thanks in advance.

[Steven_H.]

Mark,

You are correct; the LV 5.1 container does leave some stray files, and that
is indeed a bug. Here is the URL of a KnowledgeBase article (1M9AOOFP) that
describes the problem:

http://digital.natinst.com/public.nsf/web/lastweek/862567530005F09E8625678C005C3E98?OpenDocument

Attached to that article is a quick fix for the problem. The problem will
also be resolved in future versions.

Regards,

Steven Harrison
National Instruments

[Mark T.]

The "quick fix" only fixes the problem when you run a VI from LabView. If
you use the LabView Application Builder to build an EXE and redistribution
package you will still have the same problem. The redistributable LabView
Run Time Engine contains the old ole_lv5container DLL. I don't see a way to
change the version of the DLL that gets redistributed (by using the LabView
Application Builder and LabView Run Time Engine) based on the "quick fix".
And
speaking of versions, the new "ole_lv5container.dll" file has the same
version as the one that originally came with LabView 5.1 (1.0.0.1). This
makes it difficult to replace the old DLL even with a custom setup program
because
the versions are the same.


Steven Harrison wrote in message
new
s:384ef671@newsgroups.ni.com...
>
> Mark,
>
> You are correct; the LV 5.1 container does leave some stray files, and
that
> is indeed a bug. Here is the URL of a KnowledgeBase article (1M9AOOFP)
that
> describes the problem:
>
>
http://digital.natinst.com/public.nsf/web/lastweek/862567530005F09E8625678C0
05C3E98?OpenDocument
>
> Attached to that article is a quick fix for the problem. The problem will
> also be resolved in future versions.
>
> Regards,
>
> Steven Harrison
> National Instruments