| Sunil,
The PRIVILEGES and DEFPRIVILEGES fields of UAI$ are designed primarily for
storing, copying, etc, privilege masks, without being too concerned about what
the individual privileges are. There was discussion about providing some sort
of conversion for these two fields, as well as for all the access-hours fields,
but schedules, resources, etc, etc. Customers would still be waiting for V3.0
to ship if we'd put in it everything that everyone wanted!
UAI$ provides fields like .NETMBX, .TMPMBX, .DEFTMPMBX, etc, for all the
individual privileges. These fields have value 1 if the user has that
privilege, and 0 if they don't. Maybe those will serve your purpose?
If you really need to "decode" the privilege bit mask, then it's pretty easy
to write a little script to do it, using those wonderful FN$ functions :-)
Scott
|
| Hi Scott,
I was going to suggest that the customer actually check for the
required privs. using UAI$.<priv. name>. I just thought that there may
have been a lexical function that did the translation.
You know the old saying give them an inch and they want a mile.
>If you really need to "decode" the privilege bit mask, then it's pretty easy
>to write a little script to do it, using those wonderful FN$ functions :-)
Wonderful you say, I thought they are the best thing since before
slice bread :-).
Thanks
Sunil
|