Pokertracker en Ongame

Tienes que tener la base de datos con tu nick y después Statistics.



Si no te deja hacer estos tres primeros pasos cierra antes el pokertracker:



En tu cliente de OnGame:

- Vas a Statistics->Advanced->Create Statistics File

- Si tu nick es hippitro llámale a la base de datos hippitroStatistics

- Selecciónala en Statistics->Advanced->Select Statistics File



Ahora abre el PT:



- En Auto-Import PokerRoom vete a Configure Database Files. En la carpeta Resources\Databases de tu cliente de Ongame tienes las bases de datos. Selecciona la tuya.



A ver si así te funciona.



Saludos.

A ver... largo, aviso: hasta ahí ya había llegado, aunque parece que no me he explicado bien, voy a tratar de remendarlo... cuando lanzo el PT me sale este mensaje de error: ODBC Driver - The SQLite 3 ODBC driver has not been loaded yet. Please read the help for this window for instructions on how to do this. If you continue to have problems, please contact [email]support@pokertracker.com[/email]. Yo, ke soy un niño obediente le doy a help y sale un tutorial de estos del pt con un link ke lanza la descarga del SQLite ODBC Driver, lo instalo y según el tutorial del pt debería "Once you have downloaded the SQLite drivers setup files to your hard drive, double-click on the file you downloaded to install the files and follow the directions provided." ... y ahí me pierdo. En la carpeta donde se ha instalado el ODBC Driver hay un "view Readme" pero es ahí donde mis conocimientos de informatica me dejan tirado. Lo pasteo:

SQLite ODBC Driver

------------------

This is an experimental ODBC driver for the wonderful SQLite 2.8.*

Database Engine/Library. So far it is more a proof of concept and might

contain lots of memory leaks and all other kinds of bugs. Thus I highly

appreciate any feedback.

The current source can be downloaded from

[url]http://www.ch-werner.de/sqliteodbc/sqliteodbc-*.*.tar.gz[/url]

WIN32 binaries (the ODBC driver DLL, install/uninstall programs) are in

http://www.ch-werner.de/sqliteodbc/sqliteodbc-win32.zip

The binaries were made with SQLite 2.8.13, MS VC++ 6.0 and tested on

Windows NT 4.0 with the query tool of MS Excel 97, with

StarOffice 5.2 and OpenOffice 1.1.

Unzip the archive into a temporary directory and execute the INST.EXE

program. This installs the SQLite ODBC driver and creates a System DSN.

To remove the driver use the UNINST.EXE program. To create a SQLite

data source use the ODBC control panel applet and provide the name of

the SQLite database file to be worked on as an absolute pathname including

the drive letter, eg as "C:\TEMP\SQLite.DB". The busy (or lock) timeout

for the database can be specified in the respective field. If empty

a default value of 1000 milliseconds is used.

Other tests were made on Linux with the "isql" command line tool and the

"DataManager" GUI tool of unixODBC 2.1.0.

Since October 14th, 2001, the driver supports the data types SQL_INTEGER,

SQL_TINYINT, SQL_SMALLINT, SQL_FLOAT, SQL_DOUBLE, SQL_DATE, SQL_TIME,

SQL_TIMESTAMP, and SQL_VARCHAR.

Since May 25th, 2002, SQL_LONGVARCHAR is available but rather

experimental. That type is used for SQLite schema containing text

or varchar with a size specifier larger than 255.

The data type mapping obtains per-column meta information from the

"PRAGMA table_info=..." SQLite statement. If SELECTs are used which

contain columns for which the table qualifier cannot be determined,

no meta information for data type mapping is available and therefore

the database source data type will be SQL_VARCHAR or SQL_LONGVARCHAR

which usually maps to SQL_C_CHAR.

Restrictions of data type mapping:

- Integer and floating point columns in the database are reported

as NULLs when no digit seen in the column, otherwise all digits

up to end of string or non-digit are interpreted as the value,

i.e. '10blurk' is ten, '0blurk' is zero, but 'blurk' is NULL.

- Format for SQL_DATE is YYYY-MM-DD or YYYYMMDD

- Format for SQL_TIME is hh:mm:ss or hhmmss

- Format for SQL_TIMESTAMP is

YYYYMMDDhhmmss[fraction]

or YYYY-MM-DD hh:mm:ss[.fraction]

or hh:mm:ss[.fraction] YYYY-MM-DD

The fractional part is expressed as 1E-09 seconds

- The driver puts the ODBC string representations for date/time,

(eg for "{ts '2001-10-10 12:58:00'}" the substring within the

single quotes) directly into the SQLite column

Since November 17th, 2001, configure/libtool is used for the Un*x

version which should automatically find the SQLite and unixODBC

(or iODBC) header files and libraries. Do the usual

$ ./configure && make

followed by

# make install

in order to get /usr/local/lib/libsqliteodbc.so.

Of course, you should have installed the unixODBC (or iODBC)

development RPMs since the ODBC header files are required for

the build of the SQLite ODBC driver.

Since May 15th, 2003, (version 0.51), there are two versions

of the driver for Win32 platforms: the first (sqliteodbc.dll)

linked against ISO8859-1 SQLite library exporting ODBC/SQL ANSI

functions, and the second (sqliteodbcu.dll) linked against UTF-8

SQLite library exporting ODBC/SQL UNICODE functions.

The UNICODE version is experimental and allows to turn off

wide character SQL data types by its configuration dialog

(checkmark labelled "No WCHAR"). So far it has been only

tested on Win32.

To setup a SQLite data source using unixODBC ([url]www.unixodbc.org):[/url]

1. Add the driver to /etc/odbcinst.ini:

[SQLite]

Description=SQLite ODBC Driver

Driver=/usr/local/lib/libsqliteodbc.so

Setup=/usr/local/lib/libsqliteodbc.so

2. Add a DSN to your private ~/.odbc.ini:

[mysqlitedb]

Description=My SQLite test database

Driver=SQLite

Database=/home/johndoe/databases/mytest.db

# optional lock timeout in milliseconds

Timeout=2000

For iODBC (iodbc.org, only versions 3.0.[56] tested) do the

following steps:

1. Add the driver to /etc/odbcinst.ini:

[ODBC Drivers]

...

SQLite=Installed

...

[SQLite]

Driver=/usr/local/lib/libsqliteodbc.so

2. Add a DSN to your private ~/.odbc.ini:

[ODBC Data Sources]

...

mysqlitedb=SQLite

...

[mysqlitedb]

Driver=/usr/local/lib/libsqliteodbc.so

Description=My SQLite test database

Database=/home/johndoe/databases/mytest.db

# optional lock timeout in milliseconds

Timeout=2000

Python sample usage with eGenix mx-Extension

(see http://www.lemburg.com/files/python/mxODBC.html)

$ python

>>> import mx.ODBC.unixODBC

>>> dbc=mx.ODBC.unixODBC.connect("mysqlitedb")

>>> cur=dbc.cursor()

>>> cur.execute("create table foo (id int, name string)")

1

>>> cur.execute("insert into foo values(1, 'Me')")

1

>>> cur.execute("insert into foo values(2, 'You')")

1

>>> dbc.commit()

>>> cur.execute("select * from foo")

>>> print cur.fetchall()

[(1, 'Me'), (2, 'You')]

>>> print cur.fetchall()

[]

>>> cur.execute("drop table foo")

1

>>> dbc.commit()

Build instructions for MS Visual C++ 6.0:

1. Extract the source tarball sqliteodbc.tar.gz

2. Extract the official SQLite 2.x.x sources in the sqliteodbc

directory which resulted from step 1. Optionally, apply the

sqlite-locale-patch-28* which matches your SQLite version

3. Setup your MSVC++ environment, ie PATH/INCLUDE/LIB, then

open a command window, cd to the sqliteodbc directory and enter:

nmake -f sqliteodbc.mak

This compiles the SQLite sources first, creates a link library

of the necessary object files, then compiles and links the ODBC

driver and the (un)install program.

4. If you'd like to create the UNICODE version of the driver, enter:

nmake -f sqliteodbc.mak clean

nmake -f sqliteodbc.mak ENCODING=UTF8

TODO:

- improve documentation

May, 1st, 2004

Christian Werner

mailto:chw@ch-werner.de

Bueno, yo de ahí no sacao nada claro... si alguien ha pasado por este problema y es tan amable... MERCI

El problema parece que es que tu versión de la ayuda del pokertracker no es la última y el enlace te lleva a la versión 2.8 del driver, y no a la 3.3.7, que es la que tengo instalada. En mi README aparecen cosas diferentes.



La nueva te la puedes descargar de:



3uvedobles.pokertracker.com/sqliteodbc_new.exe



No me deja insertar hipervínculos por ser un fish :P.



Para comprobar la versión ejecuta el archivo sqllite3 en la carpeta del driver.

GRACIAS :P ,funcionó!