PokerTracker

hi, when importing the exported old db into the new i got several of these error messages shown in the bottom window:

Unable to begin feeder import process. Reason: PokerTracker is configured to import into an outdated database. This must be corrected before an import can succeed.


edit: it also happens when auto-importing while playing. some hands are imported and some causing those errors and the hud isnt working (even the pt icon doesnt appear).

and yes, i created a new db and set it default and active.

another edit: i downloaded the w/o postgres version of pt. i didnt think i need to download postgres again. am i wrong?

just close this....my fault

ok, got a new one. hundreds of hands causing this error:

Unable to import hand. Reason: Unable to execute query: COPY holdem_hand_summary FROM STDIN;; Reason: Fatal Error (ERROR: value "2089938456" is out of range for type smallint CONTEXT: COPY holdem_hand_summary, line 1, column id_limit: "2089938456" )

the same here, iam getting thousands of this error messages.

i exported all the hands from my beta11 database and if i try to import them into a new pt3 database iam getting this:



what can i do to solve this???

Please attach some of those hand history files to a support ticket.

err...is the number shown in the error message the number of the hand?

Yes, I think so, but you could just attach one of the HH files where you are getting the error as this will hold lots of HHs.

honestly i dont have a good mind anymore to do something. i paid 90$ for nothing but errors and not working stuff

Build 2 should resolve these problems. Sorry for the inconvenience.

I installed build 2 and I'm still getting the same errors when I import my old hand histories...

Import file: G:\temp\ps NL ($0.25) 16215873522 to 16216080685.txt
2008/05/16 14:30:22: Unable to import hand. Reason: Unable to execute query: COPY holdem_hand_summary FROM STDIN;; Reason: Fatal Error (ERROR: value "2089872920" is out of range for type smallint CONTEXT: COPY holdem_hand_summary, line 1, column id_limit: "2089872920" )

any other ideas to fix this??