I have a need to not only limit the records viewable based on user login, but I would also like to limit the items in a drop down list based on that login.

This would be for Client Access to the database. For example, we could have 6 different jobs we are tracking from 3 different clients. For Ease of this example, lets say each client has 2 jobs in our database.

When that client logs in, I only want him to see his records, but even more than that, we have some drop down lists that are generated by ProjectNames. Normally this would dynamically list all 6 projects to choose from. But I would want to limit this list to just his 2 projects.

Make sense?

Thanks for the help!

Fred

You can probably make a conditional value list based on a join (relationship) based on the Account name. I have not tried this to see what externalities it might introduce, but (as this early hour) it seems as if it would work.

Steven

Steve is right make a conditional value list based on the account name (which you could store in a field) and you should be fine.

That seems to make sense to me, but Does not appear to be working.

I have a global field in my main menu that stores the currentusername. And If the CurrentUserPrivledgeSet is set to Client, then I would like only his projects to populate the drop down to select which project to go into.

But when I try to create a value list that is based on the currentusername, it says that it will not work, because it is a global field and cannot be indexed.

How exactly does this method work or is there a better method to just showing his projects? There is a field in the project for Clients Name as well which is entered data at the beginning of the project. So essentially, I want a drop down to list only projects where currentusername = clientname.

Help! Thanks

Fred