Randy,
I'm not sure if this helps, here's a situation I found myself last year and my solution:
Scope: Rewrite 20 web sites that share common data, but also have data specific to each domain.
Restrictions:
I had to keep all of the data in one database and I also had to keep all of the scripts (Cold Fusion in this example) in the same location... meaning, index.cfm for one was index.cfm for them all.
Solution (brief):
Slice the database/code into domain specific groups. On the database end, this meant having a domain specific key (as well as a "realm" -- stupid word we used -- specific key, realm being the type of site it was) that allowed for data in table X to mean "this" to one site, while meaning "that" to another.
If that's what you're thinking, let me know, if not, sorry for wasting your time.