Client SDK 2.4
I needed to get the ODBC driver out of the client sdk so that a user could link Access to an Informix table or two. I have everything working, but I'd like to set the ODBC datasource to read-only. I can't find any read-only check box. All I can find is an Options text field. I can't find any doc on this. Is there an option I can type in there that sets the connection to read-only? -- # unrm / ksh: unrm: not found # man cpio Sent via Deja.com http://www.deja.com/ Before you buy.
On Thu, 27 Jul 2000 18:17:30 GMT, mars1972@my-deja.com wrote: >I needed to get the ODBC driver out of the client sdk so that a user >could link Access to an Informix table or two. I have everything >working, but I'd like to set the ODBC datasource to read-only. I can't >find any read-only check box. All I can find is an Options text field. >I can't find any doc on this. Is there an option I can type in there >that sets the connection to read-only? why not just use a userid with only select privileges? Ciao Fuzzy #;-)
In article <3980c60a.2112046@newshost.interact.net.au>, granta@nospam.student.canberra.edu.au (Fuzzy) wrote: > On Thu, 27 Jul 2000 18:17:30 GMT, mars1972@my-deja.com wrote: > > >I needed to get the ODBC driver out of the client sdk so that a user > >could link Access to an Informix table or two. I have everything > >working, but I'd like to set the ODBC datasource to read-only. I can't > >find any read-only check box. All I can find is an Options text field. > >I can't find any doc on this. Is there an option I can type in there > >that sets the connection to read-only? > > why not just use a userid with only select privileges? > Because accessing the database through an ODBC driver is a secondary access method. There's no way I can force them to use a specific user id if they have more than one, and I can't take away write permissions for their current user id. > Ciao > Fuzzy > #;-) > > -- # unrm / ksh: unrm: not found # man cpio Sent via Deja.com http://www.deja.com/ Before you buy.
On Fri, 28 Jul 2000 12:21:50 GMT, mars1972@my-deja.com wrote: >In article <3980c60a.2112046@newshost.interact.net.au>, > granta@nospam.student.canberra.edu.au (Fuzzy) wrote: >> On Thu, 27 Jul 2000 18:17:30 GMT, mars1972@my-deja.com wrote: >> >> >I needed to get the ODBC driver out of the client sdk so that a user >> >could link Access to an Informix table or two. I have everything >> >working, but I'd like to set the ODBC datasource to read-only. I >can't >> >find any read-only check box. All I can find is an Options text >field. >> >I can't find any doc on this. Is there an option I can type in there >> >that sets the connection to read-only? >> >> why not just use a userid with only select privileges? >> > >Because accessing the database through an ODBC driver is a secondary >access method. There's no way I can force them to use a specific user >id if they have more than one, and I can't take away write permissions >for their current user id. Ah ... sounds reasonable. How about using roles? allow the userid to have the select privileges, and all the update/insert/delete privileges available through a role. Either don't tell the user the role name, or password protect it (though I can't remember if Informix offers this? I know Oracle does). Then have your apps set the role for the user when he/she logs in. This would allow the one user id to have select privileges all the time, but only get the update privileges when the role is enabled. Not a perfect solution, but I've only had one coffee this morning ;-) Ciao Fuzzy ;-)