Active X - MS Browser in a built application ?

[Bill Trump]

I placed an Active X component, MS Browser in a container on my front panel
(LabVIEW 6.0.2)... I wrote the code to back it up and then built my
Application... it works great on my development machine. However, I went to
my target machine and my application no longer worked. My target machine
does not have LabView loaded on it. The application runs, but the container
appears to be empty on my front panel.

It's as if the Active X component, MS Browser is not available on the target
machine... how can I find out what Active X components are available when I
don't have the LabView development environment available to me?

Both my target machine and development machine are running Win98SE and
IE5.0... does anybody have any tho
ughts?

Thanks,
Bill

[Randy_H]

Bill,

I found a pretty cool program called ActiveX Manager. I have not played around with it much and it comes with a 30 day trial period. Maybe it will help.

I do have one question though, do you have any other different software between you deveolpment machine and the test machine other than LabVIEW? (Office, Visual Studio, etc?)

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

[Labviewguru]

Bill,

Whenever I run into a problem with the application builder (wait, nevermind, whenever I use the application builder period!) I use a "loader" application as opposed to creating a single executable.

Here is a link to an article I wrote (but am waiting to publish) for Developer Insights that tells you how (and why) to write a loader.

This may solve your problem, and is actually pretty easy to do.

Please let us know if this solves the problem.

http://advancedtestengineering.com/Loader.htm

[Bill Trump]

Randy,

Thanks for your quick response... I found the solution today...

Besides the contents of the "\shared\LabVIEW Run-Time" directory (which I
always copy to my target machine application directory)... I now also need
the shared file "nicont.dll"... I went ahead and copied the "nicontdt.dll"
file even though it's absence did not appear to affect my application.

I know... you're all going to tell me that I should be using the
"Installer"... well, no thanks, I'd rather have at least a little control
(and understanding)... Though it would be nice if there was a place to get
information about the "required" Run-Time files to support the various
functions within a LabVIEW application. Any hints?

Bill


Randy H wrote in message
news:5065000
0000500000053990000-1027480788000@exchange.ni.com...
> Bill,
>
> I found a pretty cool program called
> href="http://www.4developers.com/xmgr/">ActiveX Manager. I have
> not played around with it much and it comes with a 30 day trial
> period. Maybe it will help.
>
> I do have one question though, do you have any other different
> software between you deveolpment machine and the test machine other
> than LabVIEW? (Office, Visual Studio, etc?)
>
> Randy Hoskin
> Applications Engineer
> National Instruments
> http://www.ni.com/ask

[Bill Trump]

Randy,

Thanks for your quick response... I found the solution today...

Besides the contents of the "\shared\LabVIEW Run-Time" directory (which I
always copy to my target machine application directory)... I now also need
the shared file "nicont.dll"... I went ahead and copied the "nicontdt.dll"
file even though it's absence did not appear to affect my application.

I know... you're all going to tell me that I should be using the
"Installer"... well, no thanks, I'd rather have at least a little control
(and understanding)... Though it would be nice if there was a place to get
information about the "required" Run-Time files to support the various
functions within a LabVIEW application. Any hints?

Bill


Randy H wrote in message
news:5065000
0000500000053990000-1027480788000@exchange.ni.com...
> Bill,
>
> I found a pretty cool program called
> href="http://www.4developers.com/xmgr/">ActiveX Manager. I have
> not played around with it much and it comes with a 30 day trial
> period. Maybe it will help.
>
> I do have one question though, do you have any other different
> software between you deveolpment machine and the test machine other
> than LabVIEW? (Office, Visual Studio, etc?)
>
> Randy Hoskin
> Applications Engineer
> National Instruments
> http://www.ni.com/ask