I know there have been many correspondences about this subject but I have a question that hasn’t been answered yet.
I want to limit the list of values that appears in a prompt. Now, I know that you can do this in designer but I need it to be done on a per user basis. I have put restrictions on tables from within Supervisor, but this doesn’t restrict the list of values that appears in the prompt (though it will not retrieve the data if the user doesn’t have access). Is there anyway to create an object with a where clause that uses the BOUSER name( i.e. customer where employee = “BOUSER”)? We have made our BOUSER names to match those in our employee table. It is annoying to show a list of values to a user that cannot access them. Any help is appreciated.
I believe that you need to use the @VARIABLE(‘BOUSER’) function to create the object that you desire.
Snezana Ogrizovic
Quad/Graphics
End User Computing/Data Warehousing Specialist ___________________________________________________________________________ I know there have been many correspondences about this subject but I have a question that hasn’t been answered yet.
I want to limit the list of values that appears in a prompt. Now, I know that you can do this in designer but I need it to be done on a per user basis. I have put restrictions on tables from within Supervisor, but this doesn’t restrict the list of values that appears in the prompt (though it will not retrieve the data if the user doesn’t have access). Is there anyway to create an object with a where clause that uses the BOUSER name( i.e. customer where employee = “BOUSER”)? We have made our BOUSER names to match those in our employee table. It is annoying to show a list of values to a user that cannot access them. Any help is appreciated.
You can create such an object, but it’s not as straightforward as it seems…
You will have to create an object that has the appropriate WHERE clause (i.e. BOUSER = @variable(‘BOUSER’) )
You can build the LOV for this object, but remember to select the BOX = AUTOMATIC REFRESH BEFORE USE.
This will force the LOV to rebuild for each user. Since the WHERE clause has the restriction, it will rebuild the LOV and bring back the restricted row set.
If you are really interested, I can probably create something off the BEACH universe in Access and see if that helps you.
Another note… You don’t have to SELECT the same object that appears in the WHERE clause.
I want to limit the list of values that appears in a prompt. I have put restrictions on tables from within Supervisor, but
this
doesn’t restrict the list of values that appears in the prompt
(though it
will not retrieve the data if the user doesn’t have access).
I’m pretty sure that is not true, since I use it in one of my universes.
The catch is, it only shows the restricted list after a refresh. So if you follow Roberts instructions on always refreshing the list of values
before use and limit the tables in supervisor you should be set.