I have one primary table with 310 records and 75 fields which I would like to share online with 35 users. Each record represents all the pertinent data about a local union, say "Local 365". This local number is a key linking field so to speak but we are not using multiple tables this way. There would three groups of user rights 1 Admin - Can edit and change\build anything 2 Regional Manager - Can view all but only edit one field 3 Staff - Can view all and edit anything except the one field that Regional Manager Changes. I also have a Staff table with our 25 staff members names and addresses etc. about 15 fields, 25 records. The Regional manager with choose a staff rep from this table. This will be his only job, to assign a staff rep to the local. In the main table, about 12 fields should be auto populated from the staff table when this assignment is made. This allows staff information to change and be quickly applied to all the locals it affects. I also have a Regional Manager Table with 4 (records) regional managers names, address, email etc. About 15 fields. A Regional Manager is assigned to the Local by the Admin user. Final Thought for development: Staff can only view, hence only edit, local unions to which they have been assigned. Regional managers can only view\edit local unions to which they have been assigned. Finally, one of the fields in the main table asks a true\false question: "Amalgamated" This means the local union has multiple employers. If Yes is checked there will be an option\icon to click which brings up the amalgamated table where the staff or admin user can edit about 15 fields, name, address, phone, email etc. This amalgamated table can serve all locals but should be sorted to present only those records pertinent to that locals number. It can be a separate table too. Each user will have his own login ID and Password. All table have been built and populated. Field names may need to change and we are flexible.