RE: LF/VIEW field level protection...

["Reeve" <news@xxxxxxxxxx>]

The easiest way is to create another LF with only the fields you want
visible.  Just use a different record format name and specify the columns
you want available for the contact information.  The "I" usage field makes a
field read-only.

-rf

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Hatzenbeler, Tim
> Sent: Friday, May 21, 2004 6:56 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: LF/VIEW field level protection...
> 
> Column...  I have a payroll file, but would like to create a view, for
> contact information... So I only need Name and Phone number....  But
here's
> the rub...  It's for an ODBC query... And we have object authority
> preventing access to the payroll file, but I would like to create a view,
> with less authority (to the view only), so other departments can see the
> contact info...
> 
> Tim
> 
> > -----Original Message-----
> > From:       midrange-l-bounces@xxxxxxxxxxxx
> > [SMTP:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Reeve
> > Sent:       Friday, May 21, 2004 3:54 PM
> > To: 'Midrange Systems Technical Discussion'
> > Subject:    RE: LF/VIEW field level protection...
> >
> > LF's are made from PF's.  LF fields *are* PF fields, subject to minor
> > manipulation.  Are you talking about column-level security?
> >
> > -rf
> >
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> > > bounces@xxxxxxxxxxxx] On Behalf Of Hatzenbeler, Tim
> > > Sent: Friday, May 21, 2004 6:30 PM
> > > To: 'Midrange Systems Technical Discussion'
> > > Subject: LF/VIEW field level protection...
> > >
> > > Can I create a LF, with a few fields,  and have a user use the view
the
> > LF,
> > > but exclude them from the PF?
> > >
> > > Tim
> > >
> > >
> > > This e-mail message, including any attachments, is for the sole use of
> > the
> > > intended recipient(s) and may contain confidential or privileged
> > > information.  Any unauthorized review, use, disclosure or distribution
> > is
> > > prohibited.  If you are not the intended recipient, please contact the
> > > sender by reply e-mail and destroy the message.
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain confidential or privileged
> information.  Any unauthorized review, use, disclosure or distribution is
> prohibited.  If you are not the intended recipient, please contact the
> sender by reply e-mail and destroy the message.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.