In an application that will run from Server8 Advanced, I have a table that is (among other things) used to populate a value list.

I want to restrict which values from the table appear in the list, based on the privilege set assigned to the current user. (Some users will see all values, some will see just one or two, others will see most but not all, etc.)

I've tried a couple of approaches, but then realized that they will fall apart as soon as there are two concurrent users.

The only solution that I've thought of that will work in multiple concurrent users is to have multiple versions of the list (for each privilege set)used on multiple versions of the layout.

I don't like that approach, and am therefore looking for suggestions from others.

Any ideas?

bkg

Add a field to the records that make up your value list that is a return-delimited list of the privilege sets that will see that record.

Then from the context in which you want to view the value list, define a global field that is set to the privilege set name upon login.

Use these two fields in your relationship do define your related value list.

Dan -

Your advice is what I was looking for. It does exactly what I want.

One thing that I'm not sure about, though...does each concurrent client maintain its own values for globals? I read a bit in the Help files that seems to hint that they do, but I'm not sure that I understood all that I read.

Edited March 8, 200619 yr by Guest

Yes, each user has their own set of globals. When one user changes a value of a global it's for his session only, it does not change the value for other users.