hiding <no access> records

[Coby Beck]

Hi,

I have used Groups, Access, and Passwords to hide some records from some
users based on a field value. However, when I open a layout as a particular
user I am faced with a slew of <no access> values for records that fail the
test. I would like just to have these records appear to be non-existent.
ie Joe the cow farmer should log in and see only cattle in the liveslock
layout, even when he searches for sheep.

What is the usual way to accomplish this surely standard task?

TIA

--
Coby Beck
(remove #\Space "coby 101 @ big pond . com")

[Marcel]

Hi Coby,

Yes, I encountered the same. I still use groups, access privilliges and
password but I also introduced a group field in every table if necessary and
use group relations to perform always a GotoRelatedRecord[] from scripts or
buttons. In this way I hide other records for other users that doesn't
belong to the group. And if a user might fall back into all records there is
always <no access>.

I must say I find it heavy stuff in the beginning but as the project makes
progress and the concept becomes clear its easy.

Marcel

"Coby Beck" <cbeck@mercury.bc.ca> schreef in bericht
news:bf7sjc$2sbf$1@otis.netspace.net.au...

> Hi,
>
> I have used Groups, Access, and Passwords to hide some records from some
> users based on a field value. However, when I open a layout as a

particular

> user I am faced with a slew of <no access> values for records that fail

the

> test. I would like just to have these records appear to be non-existent.
> ie Joe the cow farmer should log in and see only cattle in the liveslock
> layout, even when he searches for sheep.
>
> What is the usual way to accomplish this surely standard task?
>
> TIA
>
> --
> Coby Beck
> (remove #\Space "coby 101 @ big pond . com")
>
>

[Coby Beck]

"Marcel" <m.kollenaar@slo.nl> wrote in message
news:bf8gbl$c65mn$1@ID-34238.news.uni-berlin.de...

> Hi Coby,
>
> Yes, I encountered the same. I still use groups, access privilliges and
> password but I also introduced a group field in every table if necessary

and

> use group relations to perform always a GotoRelatedRecord[] from scripts

or

> buttons. In this way I hide other records for other users that doesn't
> belong to the group. And if a user might fall back into all records there

is

> always <no access>.
>
> I must say I find it heavy stuff in the beginning but as the project makes
> progress and the concept becomes clear its easy.

Could you expand on this a bit? I take it from the lack of other responses
that I definitely need a bit more elbow grease to accomplish this task...

I already have a division code in every table containing information I want
selectively displayed. So here is my plan (probably executed by any
non-newbie as fast as I can describe it..)

- Use scripts in the menu to open layouts rather than have
layouts directly available
- Use a function to match Status(CurrentLogin) to the proper
division code
- Each script will use PerformFind on the Code field to limit
the data in the found set.
- the <no access> will be a heavy handed last defense.

Is there a way to catch any user searches and further constrain the found
set?

Is the above a reasonable plan?


--
Coby Beck
(remove #\Space "coby 101 @ big pond . com")

> "Coby Beck" <cbeck@mercury.bc.ca> schreef in bericht
> news:bf7sjc$2sbf$1@otis.netspace.net.au...

> > Hi,
> >
> > I have used Groups, Access, and Passwords to hide some records from some
> > users based on a field value. However, when I open a layout as a

> particular

> > user I am faced with a slew of <no access> values for records that fail

> the

> > test. I would like just to have these records appear to be

non-existent.

> > ie Joe the cow farmer should log in and see only cattle in the liveslock
> > layout, even when he searches for sheep.
> >
> > What is the usual way to accomplish this surely standard task?
> >
> > TIA
> >
> > --
> > Coby Beck
> > (remove #\Space "coby 101 @ big pond . com")
> >
> >

>
>

[Unregistered]

If you want to just hide the words "no access", conditional format of
not IsValid(Self)
and match to background color will do the trick.