Jump to content

Dependency Path


Recommended Posts

It seems the opened VI couldn't find the dependencies where it thought they should be.  This is probably because the dependencies, or the main VI have been moved on disk in explorer, since they were last saved.  The paths to the dependencies are relative and moving them in reference to each other can cause that to happen.

 

If you are new to LabVIEW there is some free training here.

 

NI Learning Center

NI Getting Started

-Hardware Basics

-MyRIO Project Essentials Guide (lots of good simple circuits with links to youtube demonstrations)

-LabVEW Basics

-DAQ Application Tutorials

-cRIO Developer's Guide

 

Learn NI Training Resource Videos

3 Hour LabVIEW Introduction

6 Hour LabVIEW Introduction
Self Paced training for students
Self Paced training beginner to advanced, SSP Required
LabVIEW Wiki on Training

Link to comment

When you opened your VI, you should have seen a dialog looking for its dependencies. To get the error dialog that you show in your picture, you hit Cancel when it asked you to find the missing files. If you reload the VI and this time tell LabVIEW where to find the subVIs that it asks for, you can then save the VI and you won't be prompted in the future.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.