cannot find the file

[Rasputin]

I renamed one of my subVIs and after that I get the attached error message when I open the main Vi .
My application is running perfectly but I'd like to stop getting an error message so I could sleep better

Anyone have a suggestion?

Thanks,

Message Edité par Rasputin le 10-24-2006 11:49 AM

[TCPlomp]

You should save the main file!

Ton

[Rasputin]

I have already saved it, many times. As I said, the application works fine but I always have the same error message when I open the main for the first time in a LV session.

[becktho]

Do I understand correctly: There is no LV running and no open vi, then you want to open the vi by simply double-clicking it?

[Rasputin]

The error occurs when I open the VI  for the first time after opening LV. If I close the VI and reopen it, I get no error.
Double-clicking the VI with LV closed generate the same error. It's like opening the VI for the first after having launched LV.

To be clear:
- LV closed;
- LV is opened;
- The VI is opened;
- Error message;
- VI is closed but LV remain opened;
- VI is reopened and NO error.

[becktho]

I think this is due to the operating system. I use LV8.0 and have the same problem, but just if I open the vi via Windows explorer. There must be some kind of timeout in the os that causes this behaviour. In general this should not damage your software - at least I never had problems up to now.

Just open the vi via LV (open LV-IDE and then open the vi from within the LV-IDE).

[TCPlomp]

I have read somewhere, that this appears because the slow starting of LV. The OS waits on some confirmation event from LabVIEW. This waiting times out and the OS generates an error. No harm done to LV/VIs

Ton

[Rasputin]

Okay. Thank you, Ton and becktho.
My application is working perfectly, but when I show it to the team that commanded it and an error message appears, I have to listen "Hey! What is that? I thought it worked!" . Then I close the VI, reopen it and say "See? It works! Blame uncle Bill."   Hope that it won't be like this after building the .EXE.

[becktho]

I did not have problems loading the exe - so I think you should not have any problems as well.. 😉