SQL Server Performance Forum – Threads Archive

Update Trigger / Access front end

We have an Access application that worked perfectly in SQL 2000 – but once the db was migrated to 2005, the user can no longer update a table that has an "update trigger". If the trigger is disabled, the user can compelte the update. I could only resolve this issue by increasing his permissions up to SA, (dbo didn’t even work) which I obviously don’t want to do in production. Any suggestions?

---

Does the update trigger do anything special, like a BCP? Are users logging on with Windows authentication?

---

The trigger just inserts updated column data into a separate table for history. The user is using windows authentication. Thanks.

---

Is the history table in the same DB? Did you check the permissions? SETUSER ‘<domain><login>’
INSERT INTO History VALUES (x, y, z)
SETUSER ” … and see if there are any error messages.

---

]]>