permissions

Hello,
Is it better to set the permissions on a database from the login create
dialog or should i only check the public and arrange permissions on views.
Also when linking in access i see when there are no permissions set 2 tables
are still visible. Tables sysconstraints and syssegments are they any of
use?
I would like some advise on this
It's not clear to me what you're trying to do or where you're doing it
from. When you link SQL Server tables from Access, only the links are
stored in Access. You must set permissions on database objects in SQL
Server, which you can do from the Enterprise Manager or by executing
scripts. Access will not display tables that you don't have
permissions on. You should leave all systems tables alone and not link
to them in Access. They are all there for a reason, and meddling with
them will likely break things.
--Mary
On Fri, 13 Aug 2004 15:54:20 +0200, "Ezekil" <ezekil@.lycios.nl>
wrote:

>Hello,
>Is it better to set the permissions on a database from the login create
>dialog or should i only check the public and arrange permissions on views.
>Also when linking in access i see when there are no permissions set 2 tables
>are still visible. Tables sysconstraints and syssegments are they any of
>use?
>I would like some advise on this
>