Is there a timestamp field in the view? This sounds like an issue Access has with timestamp precision, where if you supply a timestamp that is too precise it has problems. See here for more detail:
Updateable view can be a challenge due to MS-Access Optimistic Locking checks. First, for each row updated by Access, MS-Access checks that each field is the same returning as what it issued - Any changes with throw a roll-back. Next if the count of record changes does not match the count that that Access expects, it will roll-back the changes.
