Re: Limiting Oracle ODBC functionality

wmeahan_at_ef0424.efhd.ford.com (Bill Meahan) writes:

>negandhi_at_io.org (Neil Negandhi) wrote:
>>We've just installed the new Oracle ODBC driver and everything seems to
>>work perfectly (we're running SQL*NET). However, before this tool is
>>released to our users we'd like to limit its functionality. Right now,
>>anyone with the driver and a little know-how can attach Oracle tables
>>in Access and start to modify the data. Is there a way to limit users
>>to read-access only? That way they could use Microsoft Query to pull
>>data into Excel without data integrity being compromised.

>Sure. Don't grant them update or insert permissions on the tables!
 

>Of course, if you want them to have update/insert with
> **some** applications but not others, you're SOL.
Not quite SOL (which I don't know, buyu guess it means stuffed) If you have v7 you are laughing. Executing procedures run with procedure owner permissions - kindof like setuid bits in UNIX.

--
---
David T. Bath       | dtb_at_ftp.bf.rmit.edu.au (mail=dtb_at_bf.rmit.edu.au)
3/175 Wattletree Rd | Snr Tech Consultant, Global Consulting Services
MALVERN 3144 VIC    | 179 Grattan St, Carlton, Vic 3053, Australia
+61 3 500 9337      | Ph:+61 3 3477411  Fx:+61 3 3470182 Mb: +61 15 824171
WWW pages incl. ORA FAQ: lynx http://www.bf.rmit.edu.au/~dtb