Did you look in that role? There are lots of general object privileges that have nothing to do with ODBC from a technical aspect standpoint. I'm not surprised that solved the issue. I think the better approach would be to trace to see what was missing originally and add that object privilege to the original role you were using.
↧