I just set this up by using the following.
User logs in with a user name, password and client ID
If all match, then a session.clientid is set to their entered client ID
All queries are run with a
WHERE whatever_you_need = '#session.clientid#'
Works great.
Chris Giminez
Owner - Cyber Scriber Web Site Design
831-728-4469
ICQ# 2628000
> Hello, all.
>
> We are working on setting up row level security for our web application.
>
> Our method involves the creation of a view which has in it only those =
> rows to which the currently logged on user should have access. This =
> table is then joined into all queries, and by virtue of the inner join =
> the user only gets to see the appropriate rows from the database.
>
> My question is, are any of you all doing this kind of row level =
> security, and if so, do you have other schemes for ensuring that each =
> user only sees the rows they should see?
>
> Thanks.
>
> Brian Cusack
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
