04-24-2007 08:43 AM
04-25-2007 10:22 AM - edited 04-25-2007 10:22 AM
Hello BC002,
It sounds like the support files are not being properly attached. Make sure that the top level VI of your project is moved over to the Startup VIs section and that everything else from the Project Files window is moved to the Dynamic VIs and Support Files window.

If this doesn't help, please provide some additional information about your build specifications.
Happy programming!
Janell R | applications engineer
Message Edited by NIJanell on 04-25-2007 10:23 AM
04-25-2007 02:25 PM


04-26-2007 01:32 PM - edited 04-26-2007 01:32 PM
Hello BCU002,
Unfortunately, I cannot see the images you tried to embed, as they are currently pointing to a location on your computer. To get those images to show up, you need to first attach the image and then edit your post to point to the website where the image uploaded. You can right-click on the attachment, choose "Copy Shortcut" and then paste that shortcut into the Insert Image script prompt.
Now, I'm not quite sure what you mean with dragging the dlls into the dependencies. Instead, add the dll as shown in the project and make sure to move it over to the Support files when building your application, as mentioned in my previous post. Thanks!

Message Edited by NIJanell on 04-26-2007 01:33 PM
04-26-2007 03:00 PM

Don't you see it now?
As for the DLL file - the ONLY way I can find the DLL file that I need is to refresh the dependencies list in my project. As I explained in my previous posts, those two DLL files came with an example vi that i downloaded from the NI website last week and they must have been embedded inside of the example because I didn't create them myself and I've since resaed the original example vi as one that's been renamed by myself. In doing so, I presume that the DLL file was inherited from the original example vi file to my own vi file. However, that's clearly not the case because every time I run the executable file that I created with the renamed example vi file in my project, it immediately launches a searchfor the DLL files that it claims are missing!!! SInce the DLL files are ONLY visible in the dependencies list, I can't transfer them to the Dynamic VI and Support files window in the Application Builder. SO, I drag them up the Source Files tree in the Application Builder to the top of the tree where the Start-up vi is located and then I can move them to the Dynamic VI and Support Files window. Those DLL files don't appaer inthe top level of the tree where the Start-up vi appears before I move it to the Start-up vi window of the Application Builder. I'll try it again.
04-26-2007 03:47 PM - edited 04-26-2007 03:47 PM

Previous post had wrong image inserted. This is the correct image:
Message Edited by BCU002 on 04-26-2007 03:48 PM
04-26-2007 05:00 PM
Janell,
I did some investigating work and located the DLL files buried in C:\VXIPNP\WinNT\Bin folder that was apparently created when I first installed rscmuk2a_lv7_3_60_02.exe and rscmu200_lv7_4_30.exe. I explored for the files from the project and included them in the tree of files and then ran the Application Builder again so thatI could include them in the Dynamic VI and Support Files window. Next time I ran the executable file, I had to go browse for the DLL file once again to complete the opening sequence but this time all I had to do was browse for the data folder where the file was found. Once that was done, a new error #107380202 occurred at RSCMU_Init_Base.vi popped up. The reason indicated is VISA: A code library required by VISA could not be located or loaded. To tell you the truth I don't have the RSCMU200 base station test equipment connected to my laptop at the time I first ran the executable file. Is this the likely cause for the error? Can you tell me what error #107380202 means?
04-27-2007 01:43 PM
Hello BCU002,
Please drag the dll files out of the dependencies section so they are on the same level as the start up VIs. This will make it so they can be moved over to the Dynamic VIs and Support files Window when creating the application.
Thank you,
Janell R | applications engineer
04-28-2007 10:06 AM
Janell,
I tried that already before you suggested it and it failed to work. So what I ended up doing is adding the file to the project as usual by browsing from the project to the folder where the DLL file was found during my special search. Then I added it to the Dynamic VI and Support Files section and then it worked fine. Now the files are still sought after when I first run the executable file but now their easier to find in the data folder that resides with the executable file folder that's created by the executable builder.
Solved my own problem that time.
Thanks for your help too.
04-30-2007 09:36 AM
Hi BCU002,
Just for completeness, the error "VISA could not be located or loaded" typically means that NI-VISA is not installed on your computer. If you are building an installer for your exe , make sure under the additional installers section you are including VISA.