Greg,

>>Have you looked into the current user/role security model to see if that can work for you? This is specifically what it's designed for.
>
>I did. Either I don't understand it fully or it doesn't meet the need. I need to filter data records by user. In the existing data there are fields that indicate who can view the record. Some users can only see a single record (actually the data they can view is spread over a number of tables but there is a key that allows the filtering). I need to be able to do something like 'select * from sometable where somefk = userskey'

MM.NET's security architecture is very extensible--many developers have added their own special security needs on top of it. If you check out the MM .NET Dev Guide topic "Security Tables" you will see the Security table contains a list of secure objects. While that may represent user interface controls by default they can represent anything you want. The table simply contains unique IDs and a description. You can create your own UI that adds security records to this table. The UserSecurity table specifies the access a User has to secure objects and the RoleSecurity table specifies the access a Role has to secure objects.

Regards,