MS Access 2010 Linked SQL Server Tables in Named Schema

Our MS Access 2010 database uses linked SQL Server 2008 tables which are in named schemas.  Users are granted rights through a Active Directory security group, the secruity group has been granted access as:  Server Roles=public;  User Mappings: db_datareader, db_datawriter, public; no securables.  The longest linked table name is 41 characters (HumanResources.EmployeeAppointmentHistory)

Tested users rights driectly within SSMS with out issues.
The linked tables in ms access are schema_tablename

Error Message in MS Access
[Microsoft][SQL Server Native Client 10.0][SQL Server]The INSERT permission was denied on the object “EmployeeAppointmentHistory “, database “<DatabaseName> “, schema “HumanResources “. (#229)

I remember reading somewhere about setting up Synomyns for all non-dbo schema objects, I have not tested that yet.
breckdahlinAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Deepak ChauhanSQL Server DBACommented:
Hi, this is only permission issue on humanresures schema and you need to grant onlyinsert rights to username

use this
: Grant select, insert on schema::humnaresources to username;

but please ensure you have database owner or admin rights to grant and revoke permissions.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
breckdahlinAuthor Commented:
The active directory security group has (select, insert, execute, update, delete) permissions on the schema.

What works is granting the user direct right to the schema verses granting those rights to a security group

i.e. <Domain>\UserName verses <Domain>\,<SecurityGroup> of which the user is a member.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.