VI crashed suddenly (VI is not compatibale)

[GerdW]

Hi N.,

Can I actually save my broken VI using this?

No, of course not!

Backups and SVN only helps when you use it right from the beginning!

Creating backups of already broken things sounds silly to me… 😄

All this discussion has one goal: you should have learned by now to save your work by using any kind of backup/SCC - for the next time you want to program something!

[TITAN-x]

Creating backups of already broken things sounds silly to me…

Why you are going so rude GerdW? You think you are faultless? All your comments are meaningless and unhelpful. Try to be gentle & humble. Helping to people this way never works. Anyways, thanks to everybody who took effort for my issue. I will rewrite the program. 

Human learn from mistakes and call them "experience".

[GerdW]

Hi N.,

Why you are going so rude GerdW?

I added an emoticon to the sentence you cited. I thought that would be enough to make clear it isn't meant "harsh"/"rude". (I admit I tend to be sarcastic or ironic, but never rude!)

You think you are faultless?

No, I made errors like missing backups too. But fortunately this is long ago… 😄

[JÞB]

You may be confusing brevity with rudeness.  Easy enough when everything is in text.  

There may be hope to recover the vi using uncommon tools and techniques.  For instance, advanced debugger environments do exist at NI. And, there is the "Heap peek"  that helps find insane objects.  If LabVIEW Crashes as soon as the vi is loaded however, there is little hope other than to recreate the vi from preexisting documentation.  Please tell me you documented what and how the vi was intended to work.  (Or, you might have learned another valuable lesson the hard way) Ouch!

[TITAN-x]

Thanks for the reply Jeff. I couldn't save the file but luckily everything was well documented. I mean subVIs, buttons, graphics and etc. So within few days I reached back where I stopped. That was a bad experience for me but thought me a lot.  So I got lesson already.