This content has been marked as final. Show 7 replies
Just create two answers and give them the authorization to only one group.1 person found this helpful
You will end up with:
- one answers at transaction level for the standard group
- one answers at total level for the standard group
This is currently my workaround solution, but I dislike it for maintenance / enhancement reasons....
thanks for your input though,
You have an other solution which is the audit.
Just add a hide column to get the user and add it in your SQL statement.
I prefer audit than to implement security.
You have more flexibility.
what do you mean by 'audit'?
From what you expand, am I presuming that you mean I; -
1. Add a column that gets user name or user group to ascertain if user should be allowed writeback
2. Hide column
And then still allow postback (yes?) but itercede some logic that picks up the hidden user / group value and IF group user = allowed THEN continue as normal ELSE do nothing??
Is this what you mean, if not then kindly explain audit??
- add a column in answer with the name of the user
- add a user column in the target table
- use it in your writeback SQL statement to update it
You can then know who is the last user who has updated the data.
You can also add a trigger on the write back table to seed an history table.
no IF THEN ELSE/security logic, just an audit to know which user has updated the data in case of
conflict or just to give a better formation.
Edited by: gerardnico on Aug 23, 2010 10:51 AM has and not have
Thanks for your input and clarification.
In this case the users should not be allowed this level of input so prohibiting the behaviour entirely is my only option, but I understand where you are coming from...
If you want, you can implement the security in the trigger ;-)
But it's more work and not very maintainable.