LabVIEW
passsword
I never stop getting frustrated with this issue. 
Never, never, NEVER password-protect a VI. EVER. I've been writing LV code for over 11 years and I have never seen a password solve a problem. And a password almost always invariably causes more problems, including yours. If you need to keep others from messing with your code create an executable. If that is not an option insist that your manager fire the next person who messes with your code. And you should always have a backup of your work. Always. That way, if you suspect someone has changed your code you can always go back to your most recent backup.
PaulG. wrote:I never stop getting frustrated with this issue.
Never, never, NEVER password-protect a VI. EVER. I've been writing LV code for over 11 years and I have never seen a password solve a problem. And a password almost always invariably causes more problems, including yours. If you need to keep others from messing with your code create an executable. If that is not an option insist that your manager fire the next person who messes with your code. And you should always have a backup of your work. Always. That way, if you suspect someone has changed your code you can always go back to your most recent backup.
I think I know of an exception to that rule.
Believe it or not, not all customers can be trusted to pay up. In my line of work, I often write "getting started code" where I put together the architecture and code up version one for the customer. Depending on the customers skill level I'll write to their level of proficiency. Since my end deliverable is source code and I have to run the app on thier machines to prove the requirements were met, password protecting the code that goes on the customer machine is a nice way to make sure we get paid. No pay, no password. Sure the cusotmer could still stiff us and forget about being able to mod the code. But getting stiffed is rare so this is one of those corner cases were our management just has to eat the project, but I don't think that has happened except in the case of a customer going bankrupt.
So when the final bill has been paid the customer get the password. They have been very accepting of this idea because until they pay the IP is technically still ours.
Ben
As it looks now rewriting is your only option. And if you manage to write the new version without abusing globals or locals, or using any ExsperssVI. I think NI actually have done you a favor
