ActiveX privileges different in Labview than Visual Basic

[ET]

Trying to make some ActiveX calls to a 3rd party app with LV 7.1.  I am able to access many methods and properties, but one of the methods I call gives me a "insufficient user privileges" error from the app.  Realizing y'all know nothing about what causes that error in the app, my question really is "If I write the exact same set of calls in Visual Basic, I don't get the error, why not?"  What does LV do differently at that level?  I have looked at the Dcom configuration manager and have set security to none on all apps, but again, since VB has no problem, it is unlikely that it would help, and sure enough, it did not.  You may say, "ask the developers ", but none of then know how LV implements it's ActiveX so they say it is Labview's fault and of course NI will say it's an incomplete implementation of ActiveX.  Any ideas?

thanks

[Philip_Courtois]

Hi ET,

The behavior of your LabVIEW application is quite interesting since any true copy of the ActiveX script from another programming language into LabVIEW has always given the same results as with the text based program. However, one thing that could be the difference it the conversion of data types, especially when the Variant data type is involved. To further troubleshoot what is going on, please submit a simple example that shows the issue. I would prefer if you could submit the Visual Basic code and the equivalent LabVIEW VI, thanks.