[Logician]

In the first look it's very close to impossibility.

If MYSQL has a "redirect" feature for tables just like webservers, one line of code would do the trick, but unfortunately it doesnt have it.

The other possible solution would be going through the entire vb scripts and make heavy modifications in there to query other user table whenever vb interrelates with user table. I really wouldnt want to be the hacker to code this! :knockedout: Even if you have the courage to do this there are "joined queries" to user table in many parts of the code and they have to be structered totally in a different way and code and algorithm would change dramatically. So at last maybe it will work but I wouldnt call this script vbulletin anymore. You can really name the script after you..

And the third possibility (IMO the most practical) is to design the structure similiar to db/dns replication (are you familiar with the concept?). You can create a script connected to a cron job that will be triggered X times a day, go through the both user tables and populate the necassary fields accordingly. For example take existing new users from one and write to the other, update lastactivity field according to highest number etc.. Still not an easy job, but at least it's more practical..