The reasons for keeping the database separate need to be good on a practical level, because keeping them separate isn't doing you any good. That situation over-complicates what would otherwise be a much simpler problem. I'm not saying that you HAVE to merge the two databases. I'm saying that you need a really good reason to NOT merge them.
You said that the tables are the same back-end. So let me ask this in a different way. Do you have ONE DB file for the data for everything but multiple different front-end files for, essentially, two different functions?
