I also received this reply from Kim Blosser
([EMAIL PROTECTED]):
 
Hi Gary, I saw your request and I am not sure that is the best or most
efficient way to do it.  I would think if you listed out a menu and then
ran a report listing out all users who have access to that menu, would
be faster.  Then you basically have your answer, just not in the format
you are looking for.  We did this a few user back to audit who has
access to what and this helped us remove routines or linked reports that
we not used. Good luck.  Please let me know if I can provide the audit
process we did.
 
Gary Hall
Clinical Applications Specialist
Estes Park Medical Center
Information Systems Department
970-577-4443
 

________________________________

From: Gary Hall 
Sent: Tuesday, April 03, 2007 10:09 PM
To: [email protected]
Subject: Report of all routines, all users 


Here's the replies & reports I've received thus far. So far Jim's look
like the closest to what I was asking for. Here's my original note, and
then the replies are below my signature. I don't think I left any
replies off, my apologies if I did!:
 
"Hello, L, does anyone have a report that will list all routines for all
users? The NPR option that lists routines by user
(MIS.USER.user.access.list) only runs for one user at a time. I tried
copying that standard report & editing, but there's too many issues to
resolve quickly. There's also a routine that lists all users who have
access to a certain routine. But I need a report of all routines per
user (preferably that I can run for one or more applications at a
time)...? Thanks!"
 
Gary Hall
Clinical Applications Specialist
Estes Park Medical Center
Information Systems Department
970-577-4443
 
>From James Hickey ([EMAIL PROTECTED]) (mis_user_rtns.npr): You can
try the attached reports.  I wrote them many years ago.  I just
re-translated them in 5.4 and they appear to still work.
 
>From Bill Mullins (USER55): Sorry I do not have exactly what you need,
but I am sending you several reports that might help you. I did not
write these, so I can not take any credit. Look at:

MIS.USER           zcus.menu.list.w.users.frag

NPR.MENU           zcus.is.menu.list.w.users.dbm

These are in MAGIC 5.5 SR2 

>From Peggy Esch ([EMAIL PROTECTED]): If you have Data
Repository there's your answer. You have the dream location, please post
if you ever leave your position!!

>From Doug McGaw ([EMAIL PROTECTED]): I tried to tackle this one years
ago by writing a report (I think out of NPR.MENU) that would show the
routines on a given menu.  It would then check and - if the routine were
actually a submenu - it would run a fragment similar to the first.
Then, if there were submenus on this, it would do it again.  I went as
far as 4 deep and getting the list out for even one user was a
time-consuming process.  And the report was monstrous.  I gave up, but
would like to know if someone has cracked this nut. 

>From Sue St. Peter ([EMAIL PROTECTED]): Look at the attached Menu.npr and
see if it gives you what you need. If not, it may give you a start. I
went ahead and sent the NuiIcon one too because I sure find that helpful
when I'm creating menus and one always makes me think of the other...
:-)





The information contained in this message may be privileged and confidential 
and protected from disclosure.  If the reader of this message is not the 
intended recipient, or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited.  If you have received this communication in error, please notify 
the sender of this communication immediately.



=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
To subscribe or unsubscribe to the meditech-l, visit MTUsers.NET.

To check the status of the meditech-l, visit MTUsers.NET.

For help, email [EMAIL PROTECTED]

Visit the MTUsers WikiPedia at MTUsers.NET/mwiki
______________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l

Reply via email to