The problem with switching tables is a known issue and you should be able to uncheck the old table in the main PAH window to get it to pick up the new table.
BrianChina wrote:Ditto all of the above. To add to the list of symptoms, I'm finding that while multitabling, that when you start a new game or table that pah picks up the players that are already in the db but not the others. Also, if a new player arrives at the table that their stats sometimes don't display for that table. Manual pah resets fixes it sometimes but not always (but sometimes multiple resets are needed and even then there's been times I've had to shut down pt to get things rolling again.
Another twist, sometimes when I get really busy I might make a note to self to do a reset but don't and when I check things 10-15 minutes later all the stats are there. I was beginning too think pah was getting sluggish due to my db size but maybe not since reading this thread since if that were so a reset shoudn't fix things up like it does.
Do you use the cache in PAH? If not, you should try it, this will speed things up a lot, especially if you have a lot of, or very large, databases. This could improve performance of picking up new players - also check your filters; if you have minimum hands set high then you won't see the new players straight away.
Options -> Preferences -> Databases.
Please note when you first build the cache it can take a long time, so run it overnight or something.
(If you are using postgres 8.3 databases, the cache won't work.)