Some methods was missing after using ActiveX Controller Wizard in LabWindows/CV.

[wlshieh]

With the same DLL, there are two methods missing when I used ActiveX Controller Wizard in CVI but I can see the metods in LABVIEW.

[Gist]

Hello wlshieh,

I have a few additional questions for you:

• What was the source language of the DLL?
• What is the nature of the two methods that are missing?
• Are you able to post the DLL so that I can try to duplicate the behavior?

Thanks in advance!

[wlshieh]

Sorry, I can not post the DLL. Is there another way for you to try to duplicate the behavior?

[wlshieh]

I believe the DLL was written in c or c++.

Both methods scan the system to return a list of currently connected devices.

[Gist]

I definitely understand how circumstances may prevent you from posting the DLL, so I will try to help you the best I can without it.  Were the functions present in the .fp that was originally created?  That is, the undertaking you have outlined usually has two steps.  First, you use the ActiveX controller wizard to generate LabWindows/CVI code from an existing ActiveX server.  Second, you create a DLL from this code to be used elsewhere.  So to reiterate my question, were the missing functions available in the first of these steps?  I would assume they were as they were available to you in LabVIEW.  This brings me to my next question.  In what environment are the functions missing?  If they are missing in CVI, why not eliminate the aforementioned second step and simply use the product of the ActiveX controller wizard?  I look forward to your responses and helping you resolve this issue as soon as possible! 

[wlshieh]

I only use the ActiveX controller wizard to generate LabWindows/CVI code from an existing ActiveX server. Could you please tell me what do you mean by environment?

[Gist]

LabVIEW, LabWindows/CVI, Visual Studio, etc. are examples of environments. If you are using the code in CVI, there is no need to build a DLL, as the code is already available to you directly from the ActiveX controller wizard. If you are using the code in LabVIEW, you mentioned that the DLL properly identifies the two functions in question, so this is not a troublesome situation either. In what environment do you encounter the situation where you are missing the two functions?

[wlshieh]

I was using the ActiveX controller wizard to generate LabWindows/CVI code from an existing ActiveX DLL. From the DLL interface document, I found that there are two functions are missing so I use LabView functions Automation Open and Invoke Node to double check. Please see attached file for the screen captures from LabView and CVI. The functions missing are FindAvmc and FindAvmcEx. Could you tell me what are the difference between CVI and LabView?

[Gist]

CVI is an environment that is based on ANSI C (text-based programming) and LabVIEW is a graphical programming language.  Now, if you are asking what is the difference between CVI and LabVIEW with regard to these two functions, that is the very purpose of this thread to begin with.  Thank you for the helpful screen shots to illustrate the behavior you are experiencing!  It seems to me that the LabVIEW screenshot may come from exploring the "existing ActiveX DLL" while the CVI screenshot may relate to the result of the ActiveX controller wizard on that same DLL.  Is this indeed the case?  If so, how does CVI behave when you try to interact with the "existing ActiveX DLL directly" (sans ActiveX controller wizard)?

[wlshieh]

1. Yes, It is the case.

2. You requested I try to interact with the "existing ActiveX DLL directly" (sans ActiveX controller wizard). How is this done? I have not done this before.

Thanks,

William