help me get unconflicted

[Clueless1]

I have a vi that refuses to get unconflicted. (LV8.6)

It says it's in conflict with itself in the dependencies folder that says it's been moved deleted etc..  When I "resolve conflicts". I select the file that's in the right place.  It just goes into an endless confused loop that can only be stopped by hitting the red button with the x in the resolve conflicts dialog (it says then "not responding").  Do I want to end process??  Yes!. This of course causes the whole house of cards crash.  I restart the project and try again.  Here's the really stupid part.  Whan I go the conflicted file that's in the dependencies folder in the project and say "go to files view", it shows the file as being where it used to be before I moved it.  But, when I "explore selection", its not F(*&%&(%$ there!!!  Why isn't files view smart enough to know this????

When I attemp to remove both conflicted vi's from the project by draging the conflicted vi in the dependency folder into the folder with it's not so evil twin in brother (a non-autopopulating folder by the way)  and remove them both from the project.  Both pop back into the dependencies folder (con-screwed up as ever)

Help me out of purgatory!!!

Help???!!!!

[JB]

Just an idea. Open the main VI (or the caller of the conflicted VI) and then press Ctrl-Shift-Run button to recompile all VIs in memory.

[Ipshita_C]

Hi Clueless1,

When you talk of 'conflicted VIs' can you explain more clearly what type of conflict you are getting as in naming, deletion, internal error etc.? Also can you attach a screenshot of your conflict wndow as well as your project window? 

Ipshita C.

[JB]

Thank you for the 5 stars but I would be interested to know if this solved the conflict ?

[Clueless1]

Thanks for the suggestions.  I finally got past the problem.  I'm not sure what was the decisive action.  One thing for sure is I've learned that you cannot resolve conflicts by simply choosing the resolve conflicts menu item and selecting the conflicted vi and it'scorrect location.

The sort of errors were all about the vi being moved,deleted,etc.I think that the problem resolved itself when I found all of the callers and re-compiled them.

My login name sums it up but, why, if LV wants to always automatically compile and link, can IT not unload and recomplle when it's apropriate to do so, like if all of the callers are in the same project?.

Thanks