Has the user been mapped to the database? If not, that's most likely the cause of your error. If you're concerned about granting permissions. If the user needs to select or run procedure, they will need to be granted SELECT and EXECUTE at a minimum
Thanks - but that's just it. I can't find the relevant code that shows why the login needs this particular database (call it DB1). The error shows up in a web script. When I look at that line, it refers to a stored procedure call in a different database (call it DB2). There are also some views referenced in the stored procedure, but none of those views has a reference to DB1. I've also tried checking triggers on any of the tables called in the procs or views. No reference to DB1 there, either.
Do you know where I might be failing to look to confirm the dependency on this database?
"I love spending twice as long and working twice as hard to get half as much done!" – Nobody ever.
"Operator! Give me the number for 911!" - Homer Simpson
"A SQL query walks into a bar and sees two tables. He walks up to them and says 'Can I join you?'"