LabVIEW confuses subVIs in different paths but have same name? -

I'm using some runners which others have written, so this is a few historical issues.

I have the problem that if two different subveys are different, then it is stored in different places, but it has the same name.

It seems that sometimes Laboofease confuses them both, and the link jumps from one to the other, because the two subdivisions are different, it creates errors.

So my question is: Is this something real? This calls the Subway to Libavi with their filename instead of the full file path. Or can I describe some untrue and may be due to other issues.

Thank you!

There are two different things here. The first thing is that LV remembers that every file that uses something , And there are three ways to store that way (assuming I am not forgetting any one):

1. Logicals are folders like vi.lib, where The base folder is represented by a name (hence the path is stored as ".vilib. \ ... \ myVI.vi"). When you go to a different LV version, it allows you to call the correct file.
2. How is it related that L.V. Normally saves paths, so if VI is a call VI B and they are in the same folder, then the path of B inside A will be stored in the form of "..BIBI".
3. Absolute I believe this is reserved for VI only, which is stored in a different quantity, but does not match the first rule.

   If for any reason the LV file is not found, where it is considered, it will already take it to memory or try to search for it at other places, On which you will receive a search dialogue The other thing is that only one specific six names in memory at any one time. If you load two six with the same name, then you will get a conflict and solve it, as you have seen. This L.V. Not being confused, only the case of a Calling VI refers to the other end with the same name and in the order in which you load them technically, I think that the LV has the full path to allow for duplicate names It may have been used, but I believe that this decision can be made for at least 20 years, so now it will not be changed, and when you consider it, it is definitely a problem Mr. Now you can Eighth reference memory name. There are also some other technical properties.

   If you have to have the same name, then what you want to do is name space, in the past, it was often used by renaming the name using prefix or suffix. These days, you usually do this by placing the sixth in a library (eg .lvlib or .lvclass). It does not modify the filename, but it forms part of a fully qualified name, which determines the collision, so it allows you to have several loops with the same name. In the case of classrooms, this is really a requirement, because it is determined which wiss will override.