The File is not a VI

[DGU]

I am using LV7.1. And I kept getting this error message "The file is not a VI" when I tried to open my program. I can open an old copy of my code, make all the changes, and run the program. Everything seems fine, until I close the program and try to open it next time, it wouldn't open. I did the same changes for 5 times! Anyone know what went wrong?

Thanks in advance.

[altenbach]

Can you attach the bad vi?

What kind of changes do you make? How do you save the changed VI?

What is you OS (windows, Mac, Linux)?

[TiTou]

Hi DGU,

The situation you are discribing is quite weird, I have never seen anything like this... Have you tried to open the old code and to do a "save as" with another name and restart developping from this ?
Is there any subVI in your code or is it all in the same VI ?

[DGU]

it is a fairly large file. I am not sure if you want to go through that. I just type CTR-S to save the vi, and I am using Windows

I did look what kind of change caused the problem. I am not sure if I find the exact cause, but here is what I find:

I have a subVI which contains several config read function to read ini file. I replaced that subVI with a similar but different one, (just read different section of ini) and after I save the program, the file size drop from 314kB to 294kB. I do not see any reason the file size should be that much different. When I ran the program, the subVI did read what it suppose to read though.

[Dynamik]

Hi DGU,

      Have you tried simply opening/saving the old VI to a new name.  Is the "old"code written in an earlier version of LabVIEW?

Cheers.

[DGU]

The VI are all written in the same version 7.1

I did more study on the code. Here is what I found: replacing that subvi wouldn't cause the problem, but if I ran the program, the file size would reduce by that amount, and then I couldn't open it any more. This program is one application of much bigger programs. It basically generate one waveform and send the waveform to AO, and acquire the respone through AI channel. My other application doing similar job (similar vi talking to hardware, the difference is # of AO/AI channel) are working fine.

[Dynamik]

Hi DGU,

The VI becomes unusable after being run?

Is it possible that the VI [accidentally] opens itself as a data file?  Are there any graphs on the FP of this VI?

What happens if you make the VI "read only" then run it?

If the size changes as a result of the logic being executed, then it's just a matter of disabling code until the problem stops.

Please share the answer when you find it.

cheers.

[DGU]

OK, finally find what happen. After I make the VI read only, then I found the error. I miss wired the config VI path, and I use default on "write config data" on close config data vi, so that messed up my vi.

Thank you very much!!