I don't think a global's value can be made default at run-time. There are many problems with using global variables and this is often discussed (the most recent one
yesterday).
However, not all is lost. If you have an ini file, I would expect it to be kept in a constant position relative to your VI or your data, so you should know where it is on your own, even without a variable, by using a relative path. If this isn't good and you HAVE to have it dynamic, you can always keep the path of the file in another file (a basic configuration file), which will have a constant path relative to your VI. Then, save the path of the ini file to the new file and read it from there when the program starts.
This would create a mess in your files, so I would think about your files should be structured before doing something like this. If you do decide to take the first method, you should be aware that when a VI is in an EXE, its path needs to be stripped an additional time, because the EXE acts like a directory. You can determine whether you're in an EXE by using the App.Kind property.
___________________
Try to take over the world!