Measurement Studio for VB6

cancel
Showing results for 
Search instead for 
Did you mean: 

Evaluation message keeps coming up

Gary,
 
Your writing of "is the graphing component found elsewhere in the barrage of CD's that come with the Labview program?" makes me think that you may not have Measurement Studio.  If you are only installing LabVIEW you will get the cwui.ocx that is used inside LabVIEW (the license is embedded in LV itself) for LabVIEW design time purposes.  You do not however have a licensed version of the MStudio cwui.ocx file.
 
The registry keys that I talked of in my last post are there to license the ActiveX control for use in programming environments that can use ActiveX controls.  When you build an application that uses the ActiveX control it embeds that license from the registry into the EXE or DLL and then you ship the OCX file along with the application.  The OCX file will not appear unlicensed in that application but it will appear unlicensed (in Evaluation) if it is then used to try and program with it on the deployment machine.  This is how ActiveX licensing works, adn how it is being used inside LabVIEW.
 
First, Do you have Measurement Studio? or do you have LabVIEW?
What are you doing your development in?  VB6? VB.NET?
 
To answer your questions:
You do not have to delete/unregister other NI OCXs or DLLs, just the CWUI.OCX is fine.
 
The machine that has the licensed version of Measurement Studio that you speak of, does it have a CWUI key in the registry on it anywhere?  Can you tell me what is under there?  What version of Measruement Studio does it have licensed on it?
 
Regards,
Jeff
0 Kudos
Message 11 of 12
(3,471 Views)
Jeff,

The package that I have is the Labview enterprise edition and it has meas. studio included in it. So I think I installed it correctly....

I called in to NI today and spoke with an engineer that led me to a fix for my problem.

The solution was to run the Measurement Studio Version 6.0 for Windows -- Update for Visual Basic 6.0 and Visual C++ 6.0 (patch)  which was found at the following link for those who may have the same problem....

http://digital.ni.com/softlib.nsf/websearch/2AAC97491D073A6C86256EEF005374CE

This patch seems to have fixed the problem, thanks to both of you for your patience and help with this issue.

Regards,

Gary

0 Kudos
Message 12 of 12
(3,467 Views)