The workflow I'm intending is for the user to choose which team they want to create a roster for and then build the roster with that team's options. The way a team is built is from very stringent rules, max 16 players and each position has a max (usually 1, 2, or 4). So the underlying mechanisms from team to team don't change, just the names of the positions, the maximum number of positions allowed and some other pieces of data about the player. I'll take a look at the SQL server idea, but I'm not very advanced and I'd prefer the least technically advanced, if slightly more work way of doing it to wrap my head around the process.