Joolz,
I had the impresssion that this was what you actually needed, but given the complexity, you will see why I withheld it. Here is what you should consider doing:
Go to the design discussion thread (under topics in "overview". There in the topic you will see, under sample designs, a design I posted that will work perfectly for what you are trying to do, with only a minor modification (adding a section or key to handle the various configurations.)
So, once you have this design, here is what you do with it:
You need to modify the design to store all of your data in a cluster that you wish to use for the program. This cluster will be retrieved from an .ini file (configuration or initialization file), stored in memory, retrieved from memory as needed, and rewritten to the file at the end of execution (or upon user selection to do so.) There are two ways to handle storing different configurations, and I will suggest the method I used with this design, which also happens to be the simplest (I live by the credo that the "l-a-b" in LabVIEW means "Lazy Ass Bastard", pardon my french.) What you will do is add a Section to the ini file for each configuration. I will leave the details of this up to you of course, but I would suggest a simple name_# scheme, or some other logical method (I used UUT model to differentiate the data.) Once you have completed the modifications, go ahead and populate the cluster with good default data, then set it to "Write Data to File" to create your .ini file. You now have a set of configuration data.
Next, you need to integrate this into your program. You will have to add an initialization step or state to your program to allow the user to select what configuration, and to populate your controls (indicators?) with these values. Oh, quick note, make sure that you make the cluster a Type Def. This will facilitate easy modifications of your data. In fact, whenever you create a cluster, you should make it a type-def (with the exception of the LabVIEW Error Handler, that should NEVER be a typedef). Once you have initialized the data, you can proceed with your program. You will of course have to prompt the user to save a configuration, or automate this at the end of the program.
If you have any further problems with this, please feel free to email me. This is a very new design (I have never seen it before) but the concept is tried and true, and works extremely well and reliably, and is an excellent substitute for globals. It also seems to be the perfect fit for your project.
Good luck
-Mike
