PokerTracker

I have about 1.5 million hands in my DB, and have had loads of issues the past two weeks. DBs getting corrupted at least 3 times. Now my DB is showing 6.5 millions hands. The statistics and winrate are accurate but the amount of hands certainly is not. I recently had to restore (again) my DB which was dated back to April, and followed all the directions in the forum for ensuring everything was clean and reset. I have played 3 sessions since the restore and for some reason it is now showing an insane amount of hands. Any insight? Please advise, thank you.

Hello,

Where exactly do you see this problem? In all the reports or just in specific one(s)? If you are talking about a Hand report, it is possible that you have Filter on Active Player option unchecked, which means you will see hands from each player's perspective. You can uncheck that option by opening the Filters link (on the left side under Report Stats) and then clicking Add New Expression Filters.

See image, thanks for reply

Did you add players to the Alias on purpose? What happens if you click the icon next to Player's name, and remove all players from the Alias, do you then see the correct amount of hands for player Sh0rtR0und?

Yes, I combined all my WPN ScreenNames into 1 alias. This has never been an issue until today. I have ~1.2-1.5 million hands total played. The odd thing is, is that the statistics and win rate appear to be the same as before other than the number of hands, and I cant figure out why. I would say that I am somewhat concerned because I have had significant issues in the past month or so with regard to my DB. I have a solid rig that is new and I don't think there should be any hardware/component issues.

Please first try resetting the report. Right-click somewhere in the top section of the report, select Configure Report and then Restore to Default.
If that doesn't help, then backup your database, upload it to a cloud sharing service (GoogleDrive, OneDrive, DropBox,...), send us the link in a Support Ticket and we'll investigate.

I was able to get this back to normal by rebuilding the cache.

Pleased to hear it and thanks for letting us know.