Using a project within another project

[Hooovahh]

---

@David-Baratheon wrote:

and make a local copy within that project folder?

---

Nope, project explorer does no file operations, it is just a way of organizing files.  My point was that if you had a top level, and a bunch of sub VIs, you don't have to drag them over one at a time, if you just drag over the main, all of the dependencies are loaded and put under the dependencies section.  But I also was suggesting other ways of adding multiple files to the project explorer quickly.

EDIT:  Oh but one other option, within a project you can do a Save As which can duplicate the whole file structure and dependencies, making a new copy of the project too.

[David-Baratheon]

So I would do it outside of labview. Just drag and drop the VI and sub VIs from folder of old project to folder of new project?

I just thought that might cause some problems on bigger programs doing it that way. Thought it might have been better to do it within LabVIEW if there was a "proper method" of doing it

Save as is ok if you want to use an old project as a basis for a new one, but I want to copy 6 VIs from 6 different projects into one project

[David-Baratheon]

Just a bit of feedback. 

I created 6 projects (five different functions plus a main project with a menu for calling the other five).

I created five autopopulating folders and directed each one to a project folder.

Because I used "main" as the main VI for each project, when I imported them all with an autopopulating folder, it raised it as a conflict.

I was only required to browse and find the specific main I was looking for, so it wasn't really very difficult to resolve, but could be difficult if you weren't the person who initially worked on the project or if you had a large complex project.

The error came up when I came to import each individual VI into the program selection menu VI.