I searched for this in all forums.
We have an executable file which runs fine on a given windows 7 laptop. When a different user logs in, the .exe's icon isn't a labview one. Clicking on it won't run it. Windows can't associate it with anything since it has an .exe extension. Not a newbie, but this one has got me.
1) Is the executable installed under "My Documents" folder? the folder path changes with user.
2) is the executable installed in a folder requiring admin rights to access?
This is probably a Windows "Permission" thing. Here is how I solved this problem:
You don't have to rebuild! Simply find the Build (which may be sitting in a folder that J Random User cannot access), drag it and its files to the Public Documents folder (you are not going to tell the users you've done this, they don't need to know), and create a Shortcut to the Executable that you put on the Public Desktop. Note you need to have enough Windows know how (and it helps to have admin rights) to do this, but when you are done, anyone logging on to that PC will see a shortcut to "My Favorite LabVIEW Program" sitting on their desktop for them to click. [It's not really on their desktop, it's on the Public Desktop, but they don't know that ...].
My only concern is including build folder into Project/resource.
Will it cause conflicts if exe has dependent dlls and other resources, included into the build? It seems they will be present in the project from multiple locations