Can't print test results as "user"

[ken_m]

Hi,

I have a program  written in Labview 6.1 by another developer. This program runs on a PC with Windows 2000 ver. 5.0 Bld 2195 SP 3. Even though this is a stand alone test station and cannot ever be connected to the internet, we have McAfee virus protection ver. 8.01 installed and running. Test data is written to an Excel spreadsheet. The spreadsheet is then stored on the hard drive and printed on a dedicated printer.

When the operator is logged on as a "user" he can run the program but he cannot print or store his test results. Also, I have noticed that all the print vi's on the function palatte are missing. Even the Excel and Word ones

When I log on as a "system admin". I can run the program, print and store the test results. Also, all the print vi's on the function palatte are present and functional. Including the Excel and Word vi's.

For security reasons, no test operator can be a system admin.

So, how can I have my test operator be a "user" or "power user" and not a "sys admin", run the test program, print and store the results.

Please note, upgrading the system or software would take an act of God (i.e. permission from the military and the customer and DSS.), so that is not an option.


I have also tried making the test operator a "power user" and he still cannot print his test results.


Thanks for your help.

Ken M
Sr. Test Engineer
CPI Inc.

[MehakD]

Hi

The following KnowledgeBase maybe helpful in guiding you how to provide full control of National Instruments products to all users:

http://digital.ni.com/public.nsf/allkb/BB393E7B361E939886256EFD007AC591?OpenDocument

Let us know if this helps!

[ken_m]

Hi,
 
Thanks for the link. I tried it and it didn't help. I am not tracing through the code to identify specifically which vi is being blocked.

Ken M
🙂

[MehakD]

Ken,

I hope the trace through the program yields some more information to you. If you do happen to find the VI that maybe causing it to not run in user mode, then I would recommend to change the access settings for that VI individually.

Let us know if it works out!