Weird file conflicts

[Intaris]

Over the last few days I've started getting some weird file conflicts in my project.

I have several different targets within the project and I do tend to re-organise my files from time to time so I'm no stranger to file conflicts themselves.  What is surprising me is that I've startied getting messages that a file is conflicting WITH ITSELF.

In this example, the paths for both "versions" of the file for resolving the conflict are exactly the same, they point to the same file.

How does LabVIEW get into a state where it thinks a file can conflict with itself?  Do we now have, in addition to multi-core functionality, have VIs with multiple personality disorders?

Shane.

[Yamaeda]

Could it be that 1 file is in the project, and the other in a .lvlib?

That'd explain how it's existing 2 times in the project.

/Y

[pincpanter]

Maybe the file location is internally composed of a "base path" and a "relative path". The two items may differ in the base-relative combination, while the compounded path is the very same.

Just a shot in the dark.

[Intaris]

No, no .lvlibs.  The paths point to THE SAME FILE in THE SAME LOCATION.

Could it be that LV gets mixed up with different types of paths, one being a windows share (\\X\) with the other one being a bound network drive (E:\)?