Greg, thanks for this info.

So did you have to modify the RBS tables in order to add a field that will allow you to filter the users's for a particular project? or you just have a combobox filled will all users so they can be assigned to projects?

Also in my case, a main office should be able to modify and report on all data for its branches.  Imagine if I would host a single database that would host customers and their branches, I would have need a way to separate the security data at least per Customers and I though of using a Customer Schema, but unfortunately the RBS relies on the "dbo" schema and there is no easy way for me to change that and keep the source files in synch with SF updates without loosing my changes.

Edhy Rijo

No changes to the RBS tables. I added tables, using the references to the SFS tables. I.e. I have a project assignment table that tracks the ID of the project and the ID of the user. Then I have a user assigned roles table that tracks the user, project and role (multiple). I chose to just use a default project, so I have a default project table (user and project). When they login I automatically set them to use the default project.



However, I could (and might eventually) provide some way to do this during login. The only problem is that I don't know what the valid project list is until AFTER they have logged in, so it would have to be a two step process or I'd have to cache something locally.



Finally, I also have a permission that indicates all project access (all branch access in your case). When in my case, these folks also have a current project, but they can simply choose any project to view. In your case, you might consider a separate little app that is just for the branch folks to use for reporting, viewing. Sometimes that's easier than making the app too flexible.



Finally, you need your app data to be branch specific. I.e. all tables with branch related data would need to be able to query on branch.



Hope that makes sense and helps.

Yes it does, thanks.  One more question if I may....

You have a permissions "All Project", but you don't know how many project they have, so how do you actually use/set this "All Project" permission?

My application is a Call Accounting System that handle all calls dialed from different booths and calculate the price and identify the dialed number and some reports.  The VFP version has been working pretty good for a couple of years, but now I need to provide the multi-branch option, and was initially thinking on hosting the data in my ISP.  Based on the license acquired by the end user, it could be a single one or multi-branch.

For now I would have to focus on finishing it in a way that every database will be at the customer site, even if it is a single user (like I do with VFP), but for the multi-branch, then the database will be at the Main Office, and the security will be shared by all branches, this way the manager in the main office can create en users for any branch, and sometimes the branches employees may work shift in 2 branches, so the security would be the same.  I may need to have a link table to link users/branches to enforce some possible security breach like you do with your projects, and provide a way for each branch to only use the data for that branch, except for the main office.

Edhy Rijo

The "All Projects" permission would be assigned to users who have access to all projects. In your situation, I'm guessing this would be to users who work at the main branch and either oversee, report on or provide some kind of support to any branch that needs it. In my case, it is assigned to a few corporate level consultants that have access to all projects and can provide support to consultant that needs it.