When setting up priviliege sets for a table using FM8.5 is there a GET
function that returns which group an AccountName belongs to? What I'm trying
to accomplish is a script step that will find all record where the
ManagerCode=AccountName for managers or UserCode=AccountName for end users.

If Get(GroupName) = "manager"
perform find where mngrcode = Get(AccountName)
Else
perform find where usercode = Get(AccountName)
Endif

Maybe there is a simpler way to accomplish this.

Also, when I restrict access at the record level using (mngrcode =
Get(AccountName) and log in using that restricted account I can scroll
through all the records but on the ones that don't belong to this manager I
see <<NoAccess>> for all fields. I would rather not be able to see those
records at all. What am I missing?

Thanks in advance,
Steve

hello.... is anybody out there??

"GSP@DCS" <info (AT) dcs (DOT) com> wrote

Get(PrivilegeSetName)

Returns the priv set name of the currently logged-in user.

To hide the "<<No Access>>" label you would need to omit from the found set
the records the user cannot access. They are not automatically suppressed,
for a variety of reasons.



"GSP@DCS" <info (AT) dcs (DOT) com> wrote

Why thank you Bill,

It always seems so obvious AFTER someone shows the way. Not sure why I
didn't see a reference to the Get(PrivilegeSetName) function.
One more thing.
In order to correct my example previously given I would...

If Get(PrivilegeSetName) = "manager"
perform find where mngrcode = Get(AccountName)
Else
perform find where usercode = Get(AccountName)
Endif

....then...

Omit Multiple (need to omit found count but cannot pass number here can I?)
ShowOmitted
an "Omit Multiple WHERE ..." would be nice

mabe a better way would be...

perform find where mngrcode <> Get(AccountName)
omit

....yes??


"Bill Marriott" <wjm (AT) wjm (DOT) org> wrote

I'm not sure I follow the specifics of your fields, but there's a few ways
to do it. You would either just directly find what the user can view, or
find what they cannot view and "show omitted only" -- whichever is easier.
You might also want to turn error capture on and trap for the instance where
the result of either of those searches is "no records found."

"GSP@DCS" <info (AT) dcs (DOT) com> wrote