Open file vi return <not a refnum> in executable

[Soana-Phikeste]

Hey there,

I have a the "Open/Create/Replace File" vi in an executable. It works perfectly fine on my development machine, both in development and in the executable. When I install it on another machine, the <not a refnum>-function returns true.

It seems to me, that the file is not opened properly, even though it exists. There is no error, indicating that there has been a problem opening the file, so I am confused.

Did any of you come across this ... bug(?) and knows what to to about it?

Thanks in advance

[Himanshu_Goyal]

Hi,

On your developement PC you have complete LabVIEW package so its working fine but on other PC you don't have LabVIEW only you are installing the installer. So my suggestion that you can check your installer builder that you are building your installer correctly or not and also check you have include all required additional installers in your installer.

[GerdW]

Hi Soana,

two notes:

- "There is no error": well, you don't use the error cluster at all. USE IT! SHOW IT! ANALYZE IT!

- Did you check the path used in the executable? Is the path correct?

Conclusion:

Use error cluster, show a dialog with error number and path in case of an error for debugging purposes!

[Soana-Phikeste]

Would I need any other additional installers for processing files than thte runtime of the LabVIEW version I am using?

[Soana-Phikeste · Accepted solution]

Now I feel very stupid.

There actually is an error - the file was not found.

I just thought that this error message (file not found) would show automatically if I did nothing to suppress error messages, like wiring an error cluster.

[GerdW]

Hi Soana,

to show the error messages is just the default setting of the development environment...

It's nice to see "I'm feeling stupid" marked as solution 😄