I've used the lvcompare function as the basis for a LabVIEW routine that lets me "point" at two folders representing two (versions of) LabVIEW Projects, which sounds like what you're attempting. The Bad News is that the lvcompare function, like the Compare tool in LabVIEW, requires that the two files have differeent names, but the Good News is that if you call this function programmatically with "wrapper" LabVIEW code, there's nothing to stop you from renaming one of the files, for example by replacing the .vi extension with .tmp, doing the Compare, and then renaming it back to .vi. Of course, you can do other things with the "wrapper", such as making lists of files that are unique in Project 1 and Project 2 (I'm calling the two comparing entities "Project", as that's what is usually in the folders I'm comparing). Another "trick" is to do a straight binary compare first (very fast, and if they're identical to-the-byte, then LVCompare will find them identical, as well). I originally had two routines, the first one did a "non-interactive LVCompare" to make lists of differing files for me, then called a similar routine where I specified the specific VI to compare interactively (so I could see what changed). I recently combined these two phases into a single routine that passes the non-interactive "Different VIs" list to the "Compare pairs of differing VIs interactively" phase. Can be quite helpful when I forget to use SVN when working from home ...
BS
