Thanks Mark.
I have to set it up so that a user can only edit one field on the
Part. I was kind of hoping field level security would do the trick,
like it implies. I was basically hoping to limit update on every
field on the table.
I second the request to be able to have field level security on
fields for read and update.
I have to set it up so that a user can only edit one field on the
Part. I was kind of hoping field level security would do the trick,
like it implies. I was basically hoping to limit update on every
field on the table.
I second the request to be able to have field level security on
fields for read and update.
--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> > I am trying to setup field level security on the Part table. One
of
> > the fields is PartNum. When I do not allow access to this field,
it
> > appears to lock it down through out Vantage 8.00.11A. Even on the
part
> > tracker screen where a user would use partnum to search by.
> >
> > Is there anyway around this?
>
> Yes, field level security is database wide. Even your BAQs will run
> differently if run by someone with inadequate permissions. As an
enhancement,
> I would love to have field security allow read access but not
update access.
>
> Now you say you want to limit part number, and I'm curious as to
why. There
> are trackers if you don't want to allow part additions, etc.
>
> Depending on your needs, there is also Process Security.
>
> Finally, you can customize the form to do the security as well.
>
> Mark W.
>