JustJay

In 8.0, when upgrading from 7.1, the installer does not install or move any Field Point drivers or vi support files. NI has a patch to take care of this until the updated drivers are put out.

Link to the patch:

http://digital.ni.com/public.nsf/allkb/B62...625709E00680BF0

I hope this helps someone. Everyone here has always been a great help to me!

If you use "Current VI's Path" then take in account that the returned path in an exectuable is of this way:

<installation dir>\<executable>.exe\<vi-name>.vi

So in the dev-env you use one "strip path" to get the directory, but in the executable you'll need TWO "strip path"...

I will give that a try this evening....

Thanks

I have written a very simple vi that uses a number variable to call various text files into a text string. It works well in the design mode. When I build my app, I include these text files, and upon install, it places them in the install directory/data/ just as I asked it to do in the app builder. When I run my app, it cannot find the text files. In the design mode, I had all my text files in a directory on my hard drive, and they were called from there. What do I do so that my vi knows to search in the \wherever\data directory after install?

Thanks for your help!

Jay

I am attempting to code a very simple program that would take temp readings from thermcouples attacthed to Feild Point Modules and using a min/max temp range, control inflow of steam to raise low temp instances. I have searched a lot of the examples and tutorials, but have yet to find anything specific to this. I am just getting started on writing this from scratch, and any guidance or help would be great! I am using LabVIEW 6.1 Development Package with LabVIEW 7.1 Express.

I am VERY new to this, but finding LabVIEW to be extremely functional. I am the one that is functionally challenged!

Thanks!

Jay

Thanks for the reply. I fully understand that I wasn't able to express exactly what I was needing. With the information you provided, I can now search through and find where and how to change this.

I am basically learning the coding process as I go without any experienced help on site. Your "stupid comments" are more helpful than you think!

Thanks

Jay

first guess  

your software is writing a *.CSV File 

solution: search the "write characters to file" VI and set the "append" input from FALSE to TRUE 

 

second guess 

your software is using a shared library (like from OpenOffice ...) which writes a REAL excel file .. 

solution: sorry, have none 

 

third guess 

your software is using ActiveX to write into an excel file: 

change your software to: 

open the existing file, read out the last used cell, start writing from there on 

 

good look 

cb

5219[/snapback]

We have an existing program the uses Labview to write to an Exel file. The ideal situation would be for the program to continually append the current file rather than to overwrite it everytime the application is invoked. Any ideas on the best way to accomplish this. I didn't write the program, so I can't give a great deal of details on how it writes the files at the moment.

Thanks!

You can find a good manual (as PDF, if you don't like the online help ...) in "your programm files dir"\National Instruments\"your LabVIEW dir"\manuals\appbldr.pdf

There is a step by step instruction how to build an application from a VI.

What about the script you wrote ? Can you please tell some more details? The exe should contain all the files LV needs to run the application (including VIs from vi.lib, etc ...), therefore LV should not ask 4 missing files ...

5178[/snapback]

My problem was more like a lack of sleep. Came in the morning, repackaged the VI as an exe and bam, up and running. Thanks for your response....I am sure that I will have a million more questions!

Jay

Totally new to LabView here, using 6.1 also. I packaged the first program I wrote as an EXE, and included the run time engine as well. After running the installer, I ran the exe that I compiled, and it opened a "Select VI File" box. After choosing the script that I wrote, it runs fine as a stand alone. What did I do, or not do that excluded the full packaging of the file in the exe package?

This is the first day of playing with LabView, and I am liking it already!

Thanks for your help. My first post on what seems like a killer forum!

Jay