ODBC connection wasn't setup to use the credential of anyone in that group.
You can check the login credential of the ODBC connection with the following
command:
cmd>osql -D<your DSN>
This ODBC connection is created on the client workstation an used normal
Windows authentication. They have access to the database to see other tables
but these new tables in schema
demand are not visiabe to them.
> ODBC connection wasn't setup to use the credential of anyone in that
> group.
[quoted text clipped - 23 lines]
>>
>> Thanks
Mary Chipman [MSFT] - 03 Jul 2008 17:00 GMT
I don't know what your security design is, but check the permissions
granted on the schema and on the tables for the database role that
you've added the users to. I assume the public role has no
permissions. Access will not display tables that the user does not
have permission on, which is why they don't show up in the UI.
--Mary
>This ODBC connection is created on the client workstation an used normal
>Windows authentication. They have access to the database to see other tables
[quoted text clipped - 29 lines]
>>>
>>> Thanks