Re: question re: linked table list

On Sun, 09 Mar 2003 19:06:46 -0800, DA Morgan <damorgan_at_exesolutions.com> wrote:

>david epsom dot com dot au wrote:
>
>> > both cases, most of the objects on the list are objects for which the
>> > connected user does not have any rights. In our case the odbcuser has
>>
>> The list is provided by the driver: Access doesn't know anything
>> about it. (And Access programmers don't know anything about
>> it :~)
>>
>> But in Access and Windows, the Browse Permission is different
>> from the R/W/Create/Delete rights. In Win 2K you can remove
>> Browse Permission from individual files. In Access you cannot
>> remove Browse Permission from individual tables. You would
>> have to ask an Oracle person what the situation is regarding
>> Browse Permissions in Oracle.
>>
>> (david)
>>
>> "Ed Stevens" <nospam_at_noway.nohow> wrote in message
>> news:g5bc6v49bii3ujrejeg1aepneun016bb2f_at_4ax.com...
>> > Sorry for the crosspost, but this is both an Oracle and MS question,
>> > as it involves odbc drivers from both.
>> >
>> > We have a new app being developed, using MS-Access as a front-end to
>> > an Oracle 8.1.7 database. We have been playing with both the MS ODBC
>> > driver for Oracle and the Oracle ODBC driver.
>> >
>> > One thing we have noticed is particularly curious. During the process
>> > of defining a linked table, you are presented with a list of objects
>> > (tables/view/synonyms) from the underlying data source. This list is
>> > different, depending on which odbc driver we are using. Further, in
>> > both cases, most of the objects on the list are objects for which the
>> > connected user does not have any rights. In our case the odbcuser has
>> > only the system privilege of 'create session' and an object privilege
>> > of 'select' on 3 particular application tables. That being the case,
>> > I would expect the list to contain only those 3 tables, plus all
>> > PUBLIC objects, plus the 'ALL_' views.
>> >
>> > So my questions are, how are these lists generated, why do they vary
>> > by odbc driver, and are there any driver configurations to control
>> > what is presented?
>> >
>
>In Oracle you can control exactly what tables, what columns, and what data
>in those tables and columns can be viewed. Same holds for insert, update,
>and delete.
>
>The only limitation is the requirements of the application.
>
>Daniel Morgan

Right. And in this case, I would guess that as far as Oracle is concerned, the application is the ODBC driver. So here I have a case of two different ODBC drivers connecting to the same database with the same userid, and thus getting the same sets of privileges. I have to assume (argh! there's that word again!) that the driver then queries the db to get a list of tables to pass to Access, which Access then uses to load a drop-down pick list that it then presents to the user for selection. Back to the original question, the list presented to the user when using one ODBC driver is different than when using the other. Same front-end (MS Access), same database, same database user, different ODBC drivers. Received on Mon Mar 10 2003 - 07:29:43 CST