You can create a table with 2 columns BranchID and GroupBID to link branches to groups. After that you can create views that JOIN that table on BranchID with other tables and filter it on GroupBID in your queries.

>I am in the process of converting my web application data from fox data to SQL 2005 and need some recommendations relating to the structure.
>
>Currently every client’s data (500 plus) is managed in its on folder with its own set of tables in a FoxPro database. Each client has its own unique identifier called BID (Branch ID) and depending on the settings of each client, the client may or may not update some or all data to another client (well more like a group). These groups can be up to 5. The data is then duplicated in the group’s database.
>
>So, it is quite easy to change the update to one SQL database instead of each folder. The retrieval of information on a group level site is the problem.
>
>The easiest solution I can think of is to have a memo field and then just populate the group bid’s the specific record is allowed to be available on. The other option is to have say 5 additional columns eg. GroupBID1, GroupBID2 .. GroupBID5. Filtering on both these scenarios according to me will be slow when querying the data.
>