I currently am running DNN version 5.04.04, that is using a custom membership provider and custom role provider.  This is a project (dnn code base, along with the custom providers code base) I have inherited from developers that are no longer with the organization. The problem I am having is that it looks like the custom role provider was not fully implemented.  So I have spend some time implementing the role provider.  All the necessary methods appear to be working.  The big problem I am having now, is that it appears that somewhere (not in the custom role provider), the DNN code base is still looking at the Roles table in the DNN database somehow and it is causing strange "permissions/roles" problems.  It appears that the custom roles provider I have implemented goes against our own database for roles, that somewhere else in the DNN core it is also looking at the "Roles" table to get many of the roles.  So it seems that overall, it calls my custom provider half the time, it is also using the old "Roles" table to get the initial roles.  And therefore since they are not synced to the roles we have in another database (custom), when a user logs in, they don't see what they have rights to see even though in their UserInfo the roles listed are correct.  The page setting permissions are also correct.  How do I know the roles from the "Roles" table are still being used?  Because if i change any of them, then strange changes with permissions occur throughout the site.  I have added to the web.config file the custom provider section.

SO MY QUESTION IS:  What have I missed? Is there something more I need to do get DNN to stop looking at the Roles table? 

Does anyone have some tips and what I should look at or settings to change?  I have struggled with this problem for quite a while and have not found a solution or reason.  Help!! 

I thank you in advance!