Can updates via ODBC be disabled while retrievals are allowed?

From: Mitchell Nussbaum <nussbm_at_dnr.state.wi.us>
Date: 1997/10/27
Message-ID: <01bce31a$bf0434b0$1705eca8@im8020>#1/1

Some of my users have Oracle tables that are updated via PowerBuilder applications. The managers of these applications are thinking of installing ODBC and MS Access on their users' workstations, to allow them to generate ad hoc queries and reports against these tables.

They are concerned, however, that some of these users will try to use Access to update the Oracle tables, circumventing the data-integrity checks that are built into our PowerBuilder applications. Can anyone suggest ways of cutting off this end-run of our system? In particular, is there are way to make an Oracle ODBC data source read-only, or to configure the Oracle Server (we are running 7.1.5 under Open VMS for AXP) to reject update transactions that come via ODBC?

(I know, of course, that we can disable ODBC updates by removing the primary keys from our tables. But I'm not sure that trick will always be feasible for us.)

Thanks for any help you can offer.

Mitch Nussbaum
Wisconsin Department of Natural Resources nussbm_at_dnr.state.wi.us Received on Mon Oct 27 1997 - 00:00:00 CST