As a matter of fact, DENY had be put on the public role. I won't have an opportunity to test it until Tuesday, but I suspect that was the issue. So thanks for your suggestion David Webb, and to K. Brian Kelley for the T-SQL which made identifying the permissions on that table an easier task. In SSMS the public role was at the very bottom and I never thought to check it.