Re: Security Handling

This is exactly the way we do it here at XXXXXX (you fill it in). Anyway the only right any of our users has is to select from the tables. Then PowerBuilder has to call stored procs for the insert, update, and deletes from the tables. We then set up roles such as developer, manager, or end-user and only certain groups get access to the procs that they are allowed to execute. It makes for a lot of procs, but you have a secure system that can only be updated with the application. The biggest problem we had was in the way PowerBuilder handles date fields and the way Oracle handles them. We ended up having to pass dates as strings and then reconverting in the proc. Let me know if you have any more questions.

John Jones			| my views are my own.........
Oracle Consultant		| no matter what company they are
john_at_iluvatar.tip.duke.edu	| coming from.


--------------------------------------------------------------------