Archives of the TeradataForum
Message Posted: Mon, 14 May 2001 @ 14:35:02 GMT
You don't need database-level privileges just to run queries in MS Access. But when you are linking or importing data via ODBC, MS Access wants to "enumerate" the objects in the database to build a selection list. (Same applies to MS Query add-in for MS Office.)
By default, the ODBC driver uses HELP DATABASE to obtain this list. That does require you to hold at least one permission on the database as a whole - but it doesn't matter which permission. For example, you can grant EXECUTE permission on a database that contains only end-user views.
Or you can configure the ODBC driver on the client PC to use SELECT from either DBC.Tables or DBC.TablesX views to build the list of objects, rather than HELP DATABASE. That method allows you to list tables from multiple databases at once (which can be a very long list for DBC.Tables).
On the other hand, managing access at the database level is typically a good practice - a lot fewer rows in AccessRights.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|