Hopefully nobody feels I'm hijacking a thread since it does indicate general thoughts...
Today this same question hit me. After all the "blood, sweat, and tears" I, and extremely helpful members of this forum and QB, have spilled creating a single app for our group, I am asking myself if splitting the app is better.
Within our group we have 2 teams that perform the same overall task for our client, but based on the differences from a merger within our client there exists slight differences in workflow. I currently built the app to include both and am trying to reference all tables and roles based on this single field.
-> Caveat -> Most team members only ever work within one team, but there are several of us that work across both teams. Additionally, data from one is not relevant to data in the other, just the workflow process is close enough.
So my question in this is:
1. Is my current app (without seeing it) worth keeping and just control all things via the single field? Then create a Team 1 role and a Team 2 role based on the reference field?
2. Take the tables in the app (25) and copy them within the app. Then take all tables and rename them to indicate Team 1 and Team 2 and assign roles this way?
3. Create two apps, basically by copying the tables with their appropriate relationships intact and assign any cross team users roles in both apps?
4. Go home with my head hung in shame, drink myself into a stupor, and cry until I am dehydrates :) -> just kidding, I do that.
