Cat, thanks for the link! The discussion () is really closely related to my problem! Unfortunately, non of the ideas provided there are handy enough to solve my problem!
Jens, after checking all the LV-Forums and NI-Sites, I tend to agree, that there might be no way to suppress the creation of such an ini-File.
I also agree, that such a ini-File can be a very useful and easy way to predefine many parameters of the application.... But in my 'special' (?) case it has a detrimental effect. In short: I have 2 Apps in a single folder and thus, 2 ini-Files. App No.1 requires a ini-file (which is provided during the application-building-process by a 'source-ini-file'), because it stores the setting of several VISA-Parameters. If the Names of the two Apps are 'unfortunate', App No.1 reads the ini-File of App No.2, which is empty or contains useless information. Thus, I had the idea to simply ( ) suppress the creation of a ini-File for App No.2....
Now, you might argue, that there are several other easy ways to overcome the problem, e.g. to set the Source-ini-File for BOTH Apps or to recode App No.1 slightly in a way that it, when it starts, searches for an ini-File with the exact App No.1-Name.
I was just wondering whether there really is no way to suppress LV to automatically create ini-files. In some way I find this unsuppressable 'behavoir' of LV to limit my 'programmatical freedom' or, to say it in a positive manner, to force me to write better code .
Thanks,
Horst