03-06-2007 08:33 PM
03-07-2007 12:24 PM - edited 03-07-2007 12:24 PM
Hi
ming0530029,
Since you are at the stage of deploying your application to the target
computer, you need to ensure that all components are properly packaged and
deployed. To do this, you will need to create a setup package that encompasses
your application and the additional dependencies (DLLs, OCXs, etc). Check
out the Distributing
Measurement Studio Applications in Microsoft Visual Studio 2003/2005 KnowledgeBase.
Now, to ensure that you have all the appropriate merge
modules in your setup application, refer to the "Measurement Studio Visual C++ Merge Modules"
help topic in the Measurement Studio Help. In particular, since you are
using the graph control, you would need to definitely look at the User
Interface section to see what corresponding merge modules should be included in
your project.
Now to address your question as to why your application
worked on a machine with LabVIEW is quite simple. LabVIEW installs several
Measurement Studio ActiveX controls including the cwui.ocx control which
contains the graph control you were working with. Thus, this ActiveX
control was present on the LabVIEW machine and so your application found that file
(and probably other dependent files that are installed with LabVIEW). The other
machine didn't have anything installed and so there was no cwui.ocx control.
You need to follow the instruction in the KnowledgeBase
mentioned earlier or refer to the Deploying Measurement
Studio Applications category in the help.
Hope this clears things up! Also, if you are curious about merge modules, check out the What is a Merge Module? KnowledgeBase (which also points to a MSDN article).
Best Regards,
Message Edited by Jonathan N on 03-07-2007 12:25 PM