PokerTracker

This must be somewhat common but I can't find a sticky or find it in a search.

When importing large Pokerstars tournaments, Pokertracker Hold'em 2 gives an error because (I think) some of the users have special characters in their username. I never got around to fixing it but the system says I have to reimport the tourn again. I think my stats are probably OK (which is all I care about; I don't care if whatshisname ended in 1065th place). I think this also might have caused me an error converting my database to PostgreSQL.

Is there an easy fix beside editing the file, finding the special characters, and changing them?

Thanks!

-Tom

Is there an easy fix beside editing the file, finding the special characters, and changing them?

That is the easiest fix.

Also, on the File > Tournament Results - Manual Entry > PokerStars window use the Customize Summary Info. to Import button and set it up to just import the names of the players that won $ or won $ and you played against. That way PT is going to try to import a lot less names and there is less chance of this error every time.

ptrack pat wrote:Also, on the File > Tournament Results - Manual Entry > PokerStars window use the Customize Summary Info. to Import button and set it up to just import the names of the players that won $ or won $ and you played against. That way PT is going to try to import a lot less names and there is less chance of this error every time.

Ok, I changed this.

I think I did have an error converting my DB to PostgreSQL. I got an error message regarding tournaments, but the rest of the conversion seemed to go correctly. Is there a way for me to export my tournaments from my old database and import them in the new?

-Tom

ptrack mike wrote:

Is there an easy fix beside editing the file, finding the special characters, and changing them?

That is the easiest fix.

Wow, don't some people play a lot of these tournaments? It seems like it'd be a major pain for MTT players.

-Tom

What was the error message you got? If there was any error it probably would have prevented the entire conversion from completing successfully so I wouldn't trust the new PostgreSQL is correct.