How can I "touch" a configuration file?

Question

I have a program that is used to write a configuration file.  I am using the "Configuration File VIs" that came with LabVIEW 8 to manage the configuration file.  I have the "Create file if necessary" boolean input wired to "True" for the "Open Config Data" VI, but I am still getting an error about the file not being found.
The VI should do the following:
Reads the data file in the current VI's directory, "config.cfg."
If the file doesn't exist, then create the file and pass the default values to the controls on the front panel.
If the file does exist then read the data file and pass the saved values to the controls on the front panel.
User adjusts the values on the front panel and clicks on "Ok" or "Cancel"
If the user clicks on "Ok" then save the values in the controls from the front panel into the configuration file.
If the user clicks on "Cancel" then do nothing.
Close the configuration file.
Why isn't it creating the necessary file when I first run this VI?  Is there anyway I can initialize a configuration file?
Thanks!
-Nic
Attachments:
AIT - Channel Configuration2.vi ‏55 KB

Answer 1

Nickerbocker wrote:
Ok, I get it.  If the program is compiled, then the path to the current vi is within the executable like:
build_dir\build.exe\my.vi
where as if it isn't built you'd get:
dev_dir\my.vi
I
found a subVI program in the forum that does a simple check to see if
the path contains a .exe and then strips if it does passes the path if
it doesn't that works great.
Thanks
-Nic
I personally always use a different approach. I have usually an application development directory structure similar to this.
MyApplication
    <myapplication>.ini
    support
          <clean myapplication>.ini
          <myapplication>.ico
    topLevel.llb
          Startup Splashscreen.vi
          Get App Root Directory.vi
          Get App Configuration Path.vi
         <some other VIs needed in the startup and intialization of my program>
     <other function specific subdirectories such as GUI, config, FileIO, DAQ, serial, etc.>
Basically Get App Root Directory.vi always strips the Current VIs path
twice and is used by Get App Configuration Path.vi to build the ini
file path and possibly by others VIs to build specific additional
support subdirectories that the installer might create. Since Get App
Root Directory is one level below the root directory in the development
environment its relative position to the root directory is always the
same irrespective of LabVIEW development system execution or
Application execution.
The <myapplication>.ini is used by the application during
debugging etc, and the <clean myapplication>.ini file is used by
the Application Builder/Project Manager to include in the application
and contains the settings as I want them to appear after first
installation on the customers system.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions