LabView application building. Application asks for FP Write(Float -IO)

[Sergey(PSU)]

I have LabView 7.0 and I have build application using it. I have tried to include everything into installer.
But after I run application (on same PC or another PC) it asks for "FP Write (Float-IO).vi" file. If I give it to the program it starts. How is it possible to avoid this. I have tried to copy this vi into dofferent directories like system32 etc, but it does not help.
Regards, Sergey.

[tst]

Find the function in your code (it may appear several times) and see where it's located (double click it to open and select File>>Save as. You'll be able to see where it is. Is it in its original location (LV directory\vi.lib\fieldpoint\polymorphic write.llb)? If not, try replacing it with the original. Then, create a new installer and reinstall your application if necessary.
You can also try force compiling the application before building it (ctrl+shift+run), but I'm not sure this will help. If all else fails, I think placing the VI in the same directory as your exe should work.
You can also place a line in the INI file of your EXE to tell it where to search for VIs.
It looks basically like:
viSearchPath=":\*;:\;C:\...\LabVIEW 7.0\:\*;:\*;:\*;"
You can modify this and place the directory where your VI is located.
BTW, you're not calling it dynamically, right?

[Sergey(PSU)]

Thanks TST,
I have checked where it is located and it is located inside polymorphic write.llb.
I have tried to compile the application, computer did something for several seconds and what should I see after it?
Sorry, I am a novice in LabView.
How can i place a line into ini file, where should I look for it?
Placing into same directory as exe file does not work.
What do you mean call it dynamically(does not ring a bell for me), sorry.
Thanks again.
Sergey.

[tst]

Apparently, your application doesn't know, for some reason, where the VI is. My guess is that is because you built it before you had the FP VI in it. So, let's try some more options:
In the application builder, there is a tab called VI settings. See if that VI is listed there. It should be. If it isn't, try recreating your application builder settings for this build from scratch.
If this still doesn't help, you can try adding the VI as a support file, although there shouldn't be any reason for having to do this.
If that didn't help:
In the LV directory, you'll see a file called LabVIEW.ini. This file holds settings for when LV runs. Open the file and find the line I mentioned. Copy it. Go to the directory of your EXE. If you've already run it you should have an INI file there with the same name as your EXE. Open it. It will probably have one line in it. Paste the line under it. See if this helps. This line tells LV where to look for VIs, so you can change the path names here if you wish.
If that didn't help, try force compiling, then saving and building your executable again. Create an installer as well. Uninstall the app (and the LV Run-time engine) from the other machine and then use your new installer.
See if this helps.
If all this didn't help, you should probably save your code as an LLB (File>>Save with options>>development distribution) and post it. It may also be a good idea to post your .bld file.

Message Edited by tst on 03-15-2005 06:02 PM

[Sergey(PSU)]

Thanks TST,
I have checked if there is a line as you mentioned in LV directory INI file and surprisingly there where no such a line. So what I did I just opened ini file in my program directory and added the line you gave me(replacing of course the path) and after that it works. Brilliant!
It has helped but the question for me is still open: is there a way in a future how to do it correct from the beginning. Of course changing the ini file is not so complicate but it would be nice to have a correct ini file included or created by installer.
Thanks. Sergey.

[tst]

Currently the application builder doesn't export INI settings automatically. Maybe the openg builder does. Hopefully this will be a feature in LV 8.
This still puzzles me. If a VI is part of your code, the app builder should automatically build it into your EXE. If it's an NI VI, it should be installed when you use the installer you created and then it would know the path on its own. You shouldn't have to use an INI setting to tell it where to look. That's why I suspect you installed the application before putting the FP VI in your VI. If it had been there, the FP functions should have been included in the installer you made.

[Sergey(PSU)]

Thanks again,
What i did step by step: Field Point software(MAX) was installed on PC, then LabView(professional) 7.0, after that I started to write program, after it was ready and checked that it works I built application(with installer and including everything possible into it like RunTime, VIs etc.).
And after installer was ready I installed it and after trying to run I've got a message about FPwrite vi .

[tst]

Sounds to me like you're doing everything fine. If the FP VI is in your code, the app builder should link to it automatically, at least on the development machine. I have no idea why this didn't happen. If anybody else has an explanation for this, I'd be happy to hear it.

[Sergey(PSU)]

Dear TST,
I have tried to use ctrl+shift+run and rebiuld application Looks like it helps.
Now it does not ask for Fp vi file.
Thanks. Sergey.