I am trying to build an EXE file in labview , in a project which selects a config.txt file from a range of folders depending on which standard my spectrum analyser will test against. I have included the folders as support source material in the build spec, but it complains about "Multiple source files have same destination ...\executable\data\config.txt" i.e all of the final config files I need included in my final transportable EXE file have the same name even though they reside in different folders. All of the labview structure used to access these standard config files is set up to use the filename 'config.txt', and my uncompiled labview program works fine.
Can anyone suggest how to overcome this problem. Re-naming each config.txt to be a unique name doesnt seem to be a viable option, since the rest of the program accesses the file called 'config.txt' once the particular config.txt is selected from the appropriate folder.
RELATIVE pathnames seem to be a problem also. My compiled EXE works if I dont include the above folders as support source material in the build, except it cant find the config files in the programmed folder RELATIVE to Current VI's path (which are found ok in the un-compiled version of my program).