LV8 Application Builder, Installer and support files questions

[jdebuhr]

What is the best way to add support files to an application?

I have my main program that I can build as an exe. I have some support files that are in a sub directory where the exe is. I have some support files in a different location (shared by other programs) the Directory structure is similair to this:

C:\my test\Test.exe

C:\my test\Support\Support1.txt

C:\my test\Support\Support2.txt

C:\Shared\Mydata.mdb

C:\Shared\Mydata2.mdb

Do I put all of the above files in my Application when I build it or do I added them when I make an installer? All are required for my application to function properly.

Dev machine is WinXP Pro with LV8.0.1, Target machines are both WinXP Pro and Win2K

[Elsa Fung]

I think you have to add them in the installer (just drag-drop them into the project, then you can add them in the installer.  Just go to the same place where you add the exe to the installer, and select My Computer, the drag-dropped files should show up), but make sure the paths you use in your VIs to access these files match with where you install it!

[jdebuhr]

---

@Elsa Fung wrote:
I think you have to add them in the installer (just drag-drop them into the project, then you can add them in the installer.  Just go to the same place where you add the exe to the installer, and select My Computer, the drag-dropped files should show up), but make sure the paths you use in your VIs to access these files match with where you install it!

---

Yes, you were right, I tried it with them built in the the app and anything in the shared foler was int he root with the app.

I had tried it earlier the way you mentioned but got an error, removed one mdb file and it worked, I reloaded LabVIEW added the file and all  is good.

thanks

[Jarrod_S.]

Hi Jeff,

A really good technique for including support files and dynamic VIs in your build is to first add them to your project. Then, put them in a virtual folder named to indicate that these are support files. You could, for instance, have a virtual folder called My Dynamic VIs or whatever where you keep all your dynamic VIs.

The trick here, then, is to include the entire virtual folder under Dynamic VIs and Support Files in the exe build specification. Whatever is currently in that folder will then get added when the exe is built. This way, if you want to add additional support files or dynamic VIs, you don't need to change your build spec. Just add those files to the virtual folder. They will automatically get included in the build along with the rest of the files in that folder. This should really help you keep track of things.

Message Edited by Jarrod S. on 05-24-2006 10:50 AM

[dj143]

Hi Jerrod,

I have a question concerning support files that similar to this issue.  I also have a variety of support files that I have application builder include with the executable program and it works well.  However, in my situation, I sell my application to a variety of customers.  The application is made unique for each customer, which is based on the support files.  In other words, the data in the support files are what defines the application for the customer.

When I create a distribution CD I update the support files and then copy them to a folder on the CD.  This way I don't have to build the application every time I prepare a customer's system.  It's very time efficient and easy to document.  The down side is that it requires the customer to manually copy the files needed for their system.  They have to do this because the support files provided when the applicaiton is installed are default files that were present when I built the applicaition; and they will not work for the current customer.

Is there a better way to do this?  For example, is it possible to have the installation process copy files from the CD instead of using the files present when the application was built?  I'm currently using Win-XP and LV 8.2

Dave

[Jarrod_S.]

When you are building an installer, there's a field in the Advanced section called Run Executable after Installation. You can include a batch file here that can copy any necessary files to the user's computer during installation.

Message Edited by Jarrod S. on 09-04-2007 10:18 AM

[ravikumarm]

Hi

I am having problem with adding the database(MS ACCESS) to builder. I trying add LabVIEW.mdb and LabVIEW.udl files to project. Everything is fine in my system. But when i am installing that application in other system i am anable to access the same database again. I know the problem with path mentioned in LabVIEW program. But i anable to solve that one. 

Please try to help me.