Yes I have set data access to true as well , however I dont see why I should have to if the link server is created automatically for replication from what I can see DATA ACCESS should be set to true, anyway I did.
When you try this in you environment remembr the type of Replication option I was trying was
Transactional Publication with updatable Subscriptions.
This allows changes to replication back to the publisher even when changes are made at the subscriber, it also allows changes to be replicated to the Subscirber even when updates is made at the Publisher.
I think part of the problem is the link server created on the distributer (repl_distributor) is run under the distributor_admin user --see Logins under Security. However the link server at the Subscriber is running under a different user.This happens automatically and there is no access to the password for these usernames.
I tried to set up my own Subscriber link server and tried to set up local to remote server mappings based on my admin user account however the link server could not connect ,I got the RPC Error message.
Also remember I am not on a network I am using my local machine which is running 2 Instanced.