LabVIEW Path Dirctory

[PalanivelThiruvenkadam]

HI LV  Experts,

My Project.

I am working in a Project where LabVIEW Modules are Called in NI TestStand in Run Time Environment.

All Complied information are stored in "C\Users\Document\LabVIEWData" by Default. when different users are Logged in the same Machine i need to compile LabVIEW Code Modules in all the User Accounts/Logins.

To Overcome this issue i have changed the "Default Data Directory" and Mapped the LabVIEW Data File.

But still i need to repeat the same in all logins (Mapping Default Data Directory)

Is there any way i can configure in single user Login and use the same in all the available Login in a machine

[crossrulz]

Compile your code modules into Packed Project Libraries (PPLs).  Then your TestStand sequences can call any public VIs inside of those PPLs using the Runtime Engine.

[Bob_Schor]

---

@PalanivelThiruvenkadam wrote:

All Complied information are stored in "C\Users\Document\LabVIEWData" by Default.

---

To allow "all users" to access my Builds (and other "compiled" data), I save compiled information in "C:\Users\Public Documents\<xxx>" (and specifying this path in the Build Specs), with Shortcuts to the Exe's save in C:\Users\Public Desktop (which is, in Windows 10, a Hidden Folder).  You can make the folders "Read and Execute" for non-admin Users if this is a concern ...

Bob Schor

[wiebe@CARYA]

I guess you can make a symbolic link (mklink) in the teststand executable's search folder, pointing to the LabVIEW lib. That should work for all users.

A ppl is probably a more decent way to fix the problem.