Re: Restricting Inserts/Updates

In article <3761BE57.48BAAB03_at_geocities.com>,   Scott Morrow <razors_edge_at_geocities.com> wrote:
> Hi!
>
> I am attempting to find a method of disabling inserts/updates to a
> number of tables EXCEPT via the Forms 4.5 application I develop. In
> other words, I need to dissallow insert/update for anyone connected to
> the database (through SQL*NET or otherwise) via anything other than
> the application itself. (Selects are fine)
>
> In this case, grants cannot be used for protection as a commonly used
> username/password/role is necessary for use of the application.
>
> Is anyone aware of a relatively easy way of accomplishing this within
> a Forms 4.5 application/Database triggers/procedures, etc? (7.3
> Database) I would be very greatful for any suggestions.
>
> As I do not have regular access to this newsgroup, any replies CC'd
to
> razors_edge_at_geocities.com would be very much appreciated.
>
> Scott
>
>

Scott,

We did this by placing a function in the form during startup to enable a database role. The role was password protected so people couldn't enable it via SQL*Plus without knowing the password.

We put this function in a library and hard coded the password in the function. Once there all forms could access it but no one knew the password.

During development, we put a dummy library function out there for the developers to include. Once the forms were shipped to production, we simply compiled them with the new library.

That's one way!

DHT Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Wed Jun 16 1999 - 17:51:30 CDT