Object specified is not creatable in test.vi

[AIR]

Hi,

My application uses ActiveX for some userinterfacing ('treeview' and 'date
and time picker'). On some machines these controls (and all other controls)
cannot be loaded for some reason.

I've build an application, build a rt engine to run the vi, but the activex
containers don't work! I also used 'Automation Open', with the same result.
Also tried to 'Import ActiveX Control' but this seems to only make a copy of
the reference...

The error created (by LV?) is:

error code: 3005 (decimal), 'Object specified is not creatable in test.vi'

A while ago there was a discusion in this newsgroup about this, did anybody
find an awnser?

Any help appreciated,

Wiebe.



+++
All machines (that work and don't work) use Win2K (5.00.2195
, SP1), LV6.0.2
(Run-Time and/or normal environment).

Only thing that seems to make a difference is non-working machines are DELL,
and working machines are not, but I only have two similar DELL labtops, so
it's probably a configuration problem.

[codeman]

When you use an ActiveX control in a LabVIEW application, it is not automatically ported with the executable. If the control is not present or not installed properly on the distribution machine, it might cause problems. You might try doing some testing with those controls on the problem systems. Can you drop them in some other environement like Word or Excel? If the controls work elsewhere but not in LabVIEW, I'd suggest uninstalling/reinstalling the runtime engine. Try installing the 6.0.2 runtime engine off the web since the one that installs with your executable from the applibs folder might still be 6.0.0. If the activeX controls don't work in other environments either, then you might try reregistering the controls or reinstalling the software they came with
.

[AIR]

Thanks for the reply.

The problem was the result of multiple problems.

1) nicont.dll and nicontdt.dll must be available for the application.
If the setup from application builder is once performed this might be the
case, but I've just copied the .exe file (and LVRT.dll)

2) some of the OCX files simply weren't there.
They can be copied just like the .exe and LVRT.dll

3) the OCX files were not registered.
This can be done using regsvr32.exe. It should be possible using windows
api's but I'm still looking for this.

Thanks again,

Wiebe.



"codeman" wrote in message
news:506500000005000000DD580000-1007855737000@exchange.ni.com...
> When you use an ActiveX control in a LabVIEW application, it is not
> automatically ported with the executable. If the
control is not
> present or not installed properly on the distribution machine, it
> might cause problems. You might try doing some testing with those
> controls on the problem systems. Can you drop them in some other
> environement like Word or Excel? If the controls work elsewhere but
> not in LabVIEW, I'd suggest uninstalling/reinstalling the runtime
> engine. Try installing the 6.0.2 runtime engine off the web since the
> one that installs with your executable from the applibs folder might
> still be 6.0.0. If the activeX controls don't work in other
> environments either, then you might try reregistering the controls or
> reinstalling the software they came with.