Problem with Permissions for multiple developers in Windows 2000

[billings11]

We have a problem where more than one developer is trying to debug on the same PC. If all permissions are reset in the NI directories everything works fine. Under my user name, if I save a top level after that it forces me to save over some vi.lib files I am using. Then when another devloper tries to open them the permissions are wrong and the admin has to reset them again. This is a very irritating and time consuming problem. It is the exact problem from the link below. Has the problem here been solved without having to manually reset the permissions every time you modify a vi? Why does labview force a save of a sub-vi just because it wants to change the permissions? We aren't changing the sub-vi i
tself. It is very time consuming and inefficient to have an admin do this reset manually, and NI should have this solved. This is in 6.1, is it better in 7.1?
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/d95e17dfa38ca8a386256b21007660d0?OpenDocument

[SVences]

Hello �

What happens if you modify the permissions of the LabVIEW Temporary Directory? Do you still need to reset the permissions every time you modify a VI?

You could try using method 2 (from the article you referenced above). It might take a little bit more time to modify the permissions of each VI and select the �Allow inheritable permissions from parent to propagate to this object� option, but you won�t need to reset the permissions this way.

S Vences