Another cross linking

[jyang72211]

Sorry all.  I had to ask another cross linking problem, but this problem is slightly different than the other ones that I asked.

For example, I have a project that contains 2 vis.  VI 1 contains a subvi called "calvi.vi" saved in "c:\folderA".  VI 2 contains a subvi called "calvi.vi" saved in "c:\folderB"

The file calvi.vi in VI 2 and VI 3 have the same name, but they are completely different vi, and they are also in different location (folderA vs folderB).  When they vis are in the project, calvi.vi show up as a conflict, since the same vi name appear in two location. 

What would I do?

[smercurio_fc]

---

@jyang72211 wrote:

Sorry all.  I had to ask another cross linking problem, but this problem is slightly different than the other ones that I asked.

---

What other cross-linking questions have you asked? I didn't see any.

---

For example, I have a project that contains 2 vis.  VI 1 contains a subvi called "calvi.vi" saved in "c:\folderA".  VI 2 contains a subvi called "calvi.vi" saved in "c:\folderB"

The file calvi.vi in VI 2 and VI 3 have the same name, but they are completely different vi, and they are also in different location (folderA vs folderB).  When they vis are in the project, calvi.vi show up as a conflict, since the same vi name appear in two location. 

What would I do?

---

If they're completely different why would they have the same name? Do they have the same functionality, but work on different data? You have a few options, depending on what the VI(s) do:

• Change the name of one.
• Create a polymorphic VI. Each instance would have a unique name, and you'd select which one you're using within VI 1 and VI 2.
• Use a project library. Project libraries allow namespacing, which would eliminate the conflict.

[jyang72211]

They are two different vi with different funtionality, but just with the same name.  Thanks!