LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Please find the VI named ...

Both solutions will not work !!!

if you rename my.vi to copy_my.vi than LabView ist looking for copy_my.vi. Same Problem with a different name. -- Copy the code... The problem is that you cannot open the VI.
0 Kudos
Message 11 of 18
(990 Views)
Well, here's a wild idea,

Post the Vi and we'll see if someone else can open it for you.....

Before handing out 1-star ratings, please take some effort to describe your problem more accurately. What does the VI do, do you have any CINs or DLL calls? VISA communication? DAQ?

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 12 of 18
(990 Views)
Oh, and check the OS file permission settings. Perhaps you no longer have permission to read or modify the file.

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 13 of 18
(990 Views)
The file is too large to post it. The last time I saved the file he also wrote all the arrays to the file. Now it has 8MB.

What does the VI...
It it the toplevel VI of our DAQ-Software. There are a lot of SubVIs for setting up the DAQ, collect and process the data, display and save them to disc.

Also sorry for the rating. Maybe that I hit a wrong button. I didn´t noticed that I rated something.

RanChan
CIN, DLL, VISA ... sorry, me is a newbie. I don´t know what you are meaning. But I think the answer is no.
0 Kudos
Message 14 of 18
(990 Views)
I've seen a few others asking about this same problem with LabVIEW 7 and 7.1 lately. As far as I've been able to figure, the VI has been corrupted. It acts like it's searching for a sub-vi with the same name as the top level VI, which you cannot have. The other posts I've read about this have not found a solution. I think you're stuck rebuilding it from scratch.

This looks like a bug in LabVIEW 7 and 7.1. Problem is reproducing it so NI can figure out a fix for it.

Ed


Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
0 Kudos
Message 15 of 18
(990 Views)
I had exactly the same pb today with my main vi.

did someone finally found some solutions? isn't there any tool to repair the vi?

I think windows did not manage to save the vi properly last time I saved it.

when trying to double click the icon or to open it via labview, the ''please find the vi named ''xxx.vi'' dialog box appears. I choose the right vi and the dialog box pop up again. and so on.

The file exist and is 1.6 MB.
I tried to change its name and to change its location on the disk or to open it from another pc. nothing works.
I don't know what to do. The latest previous version I have need one week work to be updated!

I hope your support can help me. Thank you in advance.
0 Kudos
Message 16 of 18
(990 Views)
I contacted the NI support for this problem. They told me that there is no help, no solution, no repair function. They know the problem but the cannot do anything. Sad. Really sad.

It seems that the VI is lost in time and space. I hope that you have a backup or even a hardcopy.

And folks believe me: This problem did not happen once in lifetime. I have this problem once in a month. I seems that the error occures when Labview crashs during saving the VI or one of the included sub VI. But this is only a guess.
0 Kudos
Message 17 of 18
(990 Views)
Hi,

Could one of you post an example of such a corrupted VI? I'd like to have a
look at it.

Regards,

Wiebe.

"RanChan" wrote in message
news:50650000000500000078BD0100-1079395200000@exchange.ni.com...
> I contacted the NI support for this problem. They told me that there
> is no help, no solution, no repair function. They know the problem but
> the cannot do anything. Sad. Really sad.
>
> It seems that the VI is lost in time and space. I hope that you have a
> backup or even a hardcopy.
>
> And folks believe me: This problem did not happen once in lifetime. I
> have this problem once in a month. I seems that the error occures when
> Labview crashs during saving the VI or one of the included sub VI. But
> this is only a
guess.
0 Kudos
Message 18 of 18
(990 Views)