I hope this makes sense.
There is a lot of documentation about security. If you read through it it may help you to better understand the class structure and how to manually implement security in custom situations. Don't get me wrong, we are glad to answer any questions you have out here on the forum and these are valid questions, I just did not know if you were aware of how much security documentation that existed.
When you say security documentation do you mean the Role-Based Security Help file or security documentation in general? Because I have read most of the RBS help file and very little on security in general. Everything we do is in house and not exposed to the outside world so there is little need beyond basic permissions.
Thanks. Your suggestion will help. Because what I would like to have is one central way to manage permissions and I like what RBS has to offer.
Yes.
No. These requests are scalar, so it will be fast. If you have a problem, show all of the reports and just test the security when the end-user tries to run the report.
It is the Security Help.chm file. Attached here is the latest version in case you do no have it downloaded.
The UI Type Editor class is called SecurityKeyTypeEditor. You can also call the form directly and provide the parms which would be the SecurityKeyTypeEditorDialog.
So If i understand correctly, you're telling me that i can use the SecurityKeyTypeEditor but only at design time... OR i can call the SecurityKeyTypeEditorDialog and after passing a few params i could use it at run-time. Right?
A type editor is not the solution for anything that is done at run-time unless you are writing a development tool. You are more in need of a browse dialog type of scenario than a type editor from the sound of it.