distribution with activex container

[detlefhof]

1. Question:
In your knowledge base document nr. 16BB9RJV you saa that file ole_lv5container.dll must be copied to the target PC if activex applications are used there.
On my development PC there is no such (or similar) file, but on this machine the activex control (MS Internet transfer control) works well.
2. question: Why are all controls (buttons, string input etc.) totally flat if running the program as distributed application, while they are nicely 3-dimensional running under LV development environment?
3. question: Is there a possibility to detect which resources (dll's etc.) are missing on the target machine? My program controlling 2 LOGITECH web cameras works well on my PC (where a lot of things are installed before) but
not on the target machine.
Best regards
Detlef

[Jeremy Braden]

ole_lv5container.dll is for the use of activeX containers in LabVIEW 5.x. If you would like to know more,Knowlegebase article 2JCE9HUV discusses this. (I have made a note to update 16BB9RJV)

When you distributed your application, did you install the LabVIEW run time engine? KnowlgeBase article 2H3F2HBS discusses the problems associated with just copying lvrt.dll.

I am not sure what you mean by the third question. Typically what programs do is install the dlls they need then ask the user if they are replacing an existing file. You may be interested in the following knowlegeBase that discusses how to alter the installer. 2H87BK74 Of course, this is a use at your own risk KnowlegeBase.

Jeremy Braden
Applications Engineering
National Instruments