TeeZed wrote:
In my case, I still had the original v8.6 vi, so I recreated what I did before - making multiple saves and reloads along the way. I am non-the-wiser as to where my problem arose - but it seems to be working ok now that I am back were I was before. I am pretty paranoid about it happening again.
Unsure if I encountered a bug or just a random glitch.
That's good to hear. It's hard to say what it could be. I'm glad you still had the original.
My comments for what to do when upgrading were for you if needed (which sounds like you had the backups covered), but even more so for anyone else who happens to be reading and hasn't learned the lesson the hard way yet.
There is nothing I hate more than having to redo something I already did. Not so much the lost time which is bad enough, but the feeling I am going to forget something or not do it the same way I did before. Especially if when I originally did the work was a long time ago.
I recently had this problem where I had two sets of copies of two very similar projects. They are different enough that they need two different code bases, but similar enough that I want to try to generally do things the same way in both of them. I had a copy on my PC and a copy on my PXI DAQ computer. In the process of trying to make sure both PC's had the same latest code base, I accidentally mixed up the code a bit and overwrote some newer files with older ones. And it had been a while since I made a major backup and stored it on my network drive. I spend two days redoing code to try to get the old stuff updated with all the changes I made. And those changes were from 8 months ago. Let's say I was a little ticked at myself. I'll usually make a major copy of the whole project whenever I have a good working codebase, and I'm ready to do a major change to it that may break it before I can get it to work again.
Ray's idea of zipping up the project directory is an excellent one as it will prevent the risk of having VI's get cross-linked with the wrong directory.
