VI does not open anymore

[RavensFan]

I was able to open it in LV 2010.  However, the block diagram is password protected.  There also seems to be a decoration way off to the upper left of the front panel and a button way to the lower right.  Maybe one or both of these things are causing you problems when opening.  I tried to use the code capture tool to get a screenshot of the block diagram, but it ultimately led to a series of Not Enough Memory dialog boxes.

See the attached screenshot, and also how much actual front panel is seen and not seen on the navigation window.

If you know the password, it might be possible for one of us to try to resave it.

[vbs]

Yes please any way we can restore this file will be a GREAT HELP..

the password is "BlueSky_j196"

But I have only LabVIEW 2009 is there a way to save it in 2009 format ?

[vbs]

Also The last thing I did was change somethings to the Mixed signal graph on the GUI And I suspect that this casued some issues.

could you please delete this mixed signal graph and send the vi to me in 2009 format.

[RavensFan · Accepted solution]

Try this saved as LV 2009.

I brought in the far flung controls on the front panel, as well as tried to bring together the block diagram terminals and functions a bit tighter.  Sometimes way out of range entities can cause problems with the way LabVIEW saves files.

Where you have a lot of related controls or indicators, I would recommend doing a little bit of work consolidating them into clusters.

[falkpl]

Outside of labview, windows makes shadow copies, I have used this to sabe a corrupted VI in the past, right click on the vi icon and select properties, go to previous versions tab (if you have this on your system) and select a version from a prior date when the vi did work.  As a habit you will find that ziping work each day can save you from this in the future.

[Ben]

---

@Ravens Fan wrote:

Try this saved as LV 2009.

I brought in the far flung controls on the front panel, as well as tried to bring together the block diagram terminals and functions a bit tighter.  Sometimes way out of range entities can cause problems with the way LabVIEW saves files.

Where you have a lot of related controls or indicators, I would recommend doing a little bit of work consolidating them into clusters.

---

VBS,

Be careful!

By accepting this code from Ravens Fan you are agreeing to be his servant for life concidering he may have saved your professional carreer!

No I'm kidding but decorating all of his posts with Kudos is in order.

Ben

PS Marking his post as a solution also will give him another point for this month.

[vbs]

Wow !! It is soooo goood to see this VI open again in my computer... THANKS Ravens Fan

Thanks everyone for contributing.. Kudos to Ravens Fan !!

[smercurio_fc]

---

@vbs wrote:

Wow !! It is soooo goood to see this VI open again in my computer... THANKS Ravens Fan

Thanks everyone for contributing.. Kudos to Ravens Fan !!

---

You have, of course, now learned to use backups, right?

[vbs]

I don't seem to have this feature.. Is this somthing that needs to be enabled in the Windows. We used XP so maybe this feature is not there in XP.

[vbs]

Yes, We have active directory in the server and a source control system, Both had 2 months old copies.. But lesson learnt, Thanks to the forum without a heavy price 🙂