How about having record level security. For example 2 employees enter date in one form and are only able to see their own work. Having the ability to select such security when using the security module would make everything so much faster and easier.
Within the same form requires field level security. I find the current security modal in it’s largest form very user-unfriendly with the loads and loads of checkboxes. Adding field level security…
Within the same table you can add a ‘owner’ field and use this one to select only the records belonging to the owner.
in the onvalidate event you add the user to the table.
in the sql you add the user to the select statement.
Yes I guess you are right. It would be very cumbersome. I thought of this before I realized how simple SC has made it to do this.
We use logged in variable of usr_id and in the sql of the app, add WHERE usr_id = [usr_id]
Works very well.
[QUOTE=mstopkey;19359]We use logged in variable of usr_id and in the sql of the app, add WHERE usr_id = [usr_id]
Works very well.[/QUOTE]
Yes I am also using the same field (login) from the sc_users table.
I prefer not to. If the userid needs to be changed for whatever reason you have to adjust all the tables. I know it’s simple sql but…
[QUOTE=mstopkey;19359]We use logged in variable of usr_id and in the sql of the app, add WHERE usr_id = [usr_id]
Works very well.[/QUOTE]
I’d recommend you this suggestion on applications that you need this level of security.
regards,
Bernhard