If it possible to capture a user’s login name then hold and pass this somehow to the parameters of a report so that the data returned is associated ONLY with that particular user? My report contains data for multi users and I only want them to see their own data…not anyone else’s . How difficult of a task is this? Thanks 
korzel 
(BOB member since 2004-01-20)
Not difficult at all.
Start with this topic: Using Designer to Implement Row-Level Security
What you need to check into is the use of @variable(‘BOUSER’)
Steve Krandel (BOB member since 2002-06-25)
Does this affect free-hand-SQL data providers, too?
Just curious.
cu,
olli
haupto 
(BOB member since 2004-04-16)
No, it should not.
Whenever you implement row-level security via Business Objects (Designer or Supervisor) you should not allow Freehand-SQL as well as not allowing users to modify the SQL code.
Otherwise you should implement security on the database side (which requires individual logins via the universe connection).
Andreas (BOB member since 2002-06-20)