Why does my built application create a "labview data" folder in the "My Documents" folder?

[crelf]

LV7 - I know this folder is for custom probes and error logs, but can I stop it's creation when one of my LabVIEW built exes is run? Or do I have to delete it manually every time my application is launched?

[altenbach]

I feel it is very useful if there is a default folder present for certain operation, and if it is dedicated to labview (instead of e.g. temp, etc.) there is less clutter in the file system.

You don't have to delete it, just leave it there. It won't hurt anything. 😉

Anyway....

Have you tried to define a different default data directory (options...paths)?
Put the following line in the application.ini of your built application and point it to an existing folder such as temp:

DefaultDataFileLocation=....

that should do it.

[crelf]

I personally don't have a problem with the folder being there, but my client is going to on-sell the application to their customers, and they would prefer it not be there. Thanks for the ini file setting 🙂

[Mads]

Tried using this for a built application. I verified that the .ini file was read by changing the font using keys in the same file, but the defaultDataFileLocation key does not seem to have any effect, it will still create a LabVIEW Data folder in My documents...I also changed it in LabVIEW from the options dialog and copied the key from LabVIEW.ini to the .ini-file of my application - no effect. Has anyone succeeded in using this key for a built application, if so - how did the line in the .ini-file look like?

It's annoying that NI always pushes their company and product names on us, they might as well force everyone to have a LabVIEW logo engraved on all front panels.

[Greg_McKaskle2]

....
>
> It's annoying that NI always pushes their company and product names on
> us, they might as well force everyone to have a LabVIEW logo engraved
> on all front panels.

Always? This sounds like someone's feature in LV7 has a bug in it.
Personally I think it would be cool for others to OEM LV and do custom
editors based on it. That means that most things that mention NI or LV
are changeable, but since there is only one OEM at the moment, and they
don't ship with every release, some of these things get overlooked.

Report it, and it should get set straight. On the otherhand, we have to
use something as the default, and you can't blame NI for defaulting to a
name we would like people to know.

Greg McKaskle