VI crashed suddenly (VI is not compatibale)

[TITAN-x]

Hello everyone,

I have a project which I was running my VI smoothly with no issue. While I was working on it suddenly gave an error saying : This VI is not compatible. Than LabVIEW restarted but cannot open my VI any more. So now, when I click on my VI that is programmed in LabVIEW 2016 I get the below attached error. Just for your info I am using Windows 8. 

Does anyone has any idea about it?

P.s. Because of security regulations I am not able to share the VI. Sorry about that.

[GerdW]

Hi N.,

there's an error with your VI.

Solution: use a backup of the VI or check out an older version from your SCC system…

[TITAN-x]

Hello GerW,

Thanks for your fast reply. I am not familiar with the backup procedure. If you don't mind Could you please guide me on that?

Thanks

[GerdW]

Hi N.,

you really don't know how to make backups and use them? Really?

Ok, to make a backup means:

- create a copy of your work

- store the copy in a safe place

- repeat those two steps in a regular interval

When you have trouble with your work (aka VI) you just go to your safe place and get the latest backup copy…

Did you do any backups before? If no: why not?

[TITAN-x]

Of course I know how to make back up. I usually make a copy of my VI's. But the current project came to me in last few days and before me someone else was running it. Eventually, I also didn't make a backup of the program. The problem now is I have no access to the VI. So I can't save the VI for the older version also.

Anyways, thanks for your reply.

[JÞB]

Some days Irony rears its head and roars!

"There is no memory or retentive faculty based on lasting impression. What we designate as memory is but increased responsiveness to repeated stimuli."- Nikola Tesla

I assume you are currently looking into Source Code Control repository options.

[TITAN-x]

Yes I do Jeff. Trying to find out a solution using Source Code Control.

[crossrulz]

---

@TITAN-x wrote:

Yes I do Jeff. Trying to find out a solution using Source Code Control.

---

Tortoise SVN is probably the simplest approach to SCC (integrates right into Windows Explorer).  If your company already has a good SCC system, just start using it.

[JÞB]

---

@crossrulz wrote:

---

@TITAN-x wrote:

Yes I do Jeff. Trying to find out a solution using Source Code Control.

---

Tortoise SVN is probably the simplest approach to SCC (integrates right into Windows Explorer).  If your company already has a good SCC system, just start using it.

---

And the TSVN TK by Viewpoint integrates the repo with LabVIEW very nicely

[TITAN-x]

Sorry if this is a stupid question but I have never used such programs so I have to ask you guys; I already downloaded tortoise and trying to learn how to use it but Can I actually save my broken VI using this? Eventhough I downloaded the program after things happened?