June 15, 2006 at 7:02 am
We have a user with Windows Authentication, who cannot update a table via an Access front end, that fires a very simple "update trigger" when 2 columns are updated. This trigger just doest an insert into another table to track history. We did not have the problem when the db was in SQL 2000 - just after migrating to 2005. If I increase his permissions to SA - it works, but obviously, that is not what I want to do in a production environment. Any suggestions?
June 15, 2006 at 8:00 pm
Did you make certain that, up at the server level in 2005, you authorized whatever Windows groups or users you had authorized in 2000?
Although the users or groups are recreated within your database (assuming you did a backup/restore operation since it's the easiest), the authorizations as logins are not created automatically.
Also, by what mechanism are you delivering permissions to the user. Are the permissions on that particular user? (Not recommended.) Are they assigned to a group? If the latter, is the user still in that group?
Check these first.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply