Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Preventing Write access to linked tables

Status
Not open for further replies.

Flopper

Technical User
Jan 19, 2001
140
AT
Greetings,

I'm linking a number of tables from an Oracle database through ODBC into Access 2000. When i open the tables it appears that i am able to write or alter any record upon any of the tables. Is there any way in which i can prevent this happening, i.e. only allow read-only access?

I know that i can obtain a read-only user name from the DBA but this has complications.

Regards
 
If you're using the Oracle ODBC driver, there's a checkbox to "Connect to the database in read-only mode" when you're creating the DSN. This does not exist in the Microsoft ODBC for Oracle driver.

Tranman

"Adam was not alone in the Garden of Eden, however,...much is due to Eve, the first woman, and Satan, the first consultant." Mark Twain
 
Hi,

If whoever has write access to your Access tables, then they will always have write access to your Oracle tables (unless your connection string to the Oracle tables includes a readonly user/password to the Oracle tables).

Either you restrict access to users to those you trust to write to ALL tables (including linked), or you apply the restriction at the Oracle database level, which will then apply to the MS Access link table.

I'm no expert on this, but I believe this to be accurate. (I've got the same problem linking to the company MRP system Pervasive tables).

Regards,

Darrylle




Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@yahoo.co.uk
 
I know that i can obtain a read-only user name from the DBA but this has complications.

Just because a road is harder to travel does not make it the wrong road.

Without any doubt, you should set security with the account used for the Oracle connection. You may circumvent write access through code and / or configuration. But you still have a HUGE hole in your security system that threatens the integrity of the database. Someone else can easily create their own connection string, say using ODBC to connect through a spreadsheet and still mess things up.

I am not sure what makes talking to the DBA complicated, but I hope you both can overcome your differences and do the professional thing.

Richard.
 
Thanks for all your advice. Richard, although easier said than done you're advice is will be taken.

Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top