The field level security probably would be easier to do.
Place your users into group to better manage the process.
Then figure out what fields are what on the forms that you are going to be working with. THis is done by turning on developer mode and clicking on the field in when it is in customization mode.
Then go to field security and find the table, select the field, and start disallowing (or allowing) groups/people the ability to access the field. This is why the group approach will work better for you.
Best of luck on going live!
Brz in Mpls.
Place your users into group to better manage the process.
Then figure out what fields are what on the forms that you are going to be working with. THis is done by turning on developer mode and clicking on the field in when it is in customization mode.
Then go to field security and find the table, select the field, and start disallowing (or allowing) groups/people the ability to access the field. This is why the group approach will work better for you.
Best of luck on going live!
Brz in Mpls.
--- In vantage@yahoogroups.com, "leann_37" <lmarruffo@...> wrote:
>
> All,
> We are going line in 4 weeks, and are still way too new at this. Is there a way to programmatically control by login, who can see what's on a form? Do we have to rely on field level security or customization? Our site is fanatic about covering cost fields except for a few users, and man, those fields are EVERYWHERE.
> Thanks in advance!
> - leAnn
>