Networking PT3 Q's

[pr1mo]

Just finally got my comps setup to network my pt3 off my main machine. A few questions:

When i'm playing a multi-table multi-comp session and i'm running HUD on both comps from same database and it's auto-updating does it update both databases with all hands? So if i'm playing a new player and 5 hands on one comp and 5 hands on the other will it add up to 10 on both tables?

Is it possible to access my pt3 database from an outside source? If say i'm over playing at a friends and I don't keep my database on it so I need to connect to my desktop at home?

[pr1mo]

also if i wanted to get a 3rd computer in to have 2 computers accessing this main desktop pt3 database do i just get another set of reg codes and then can i have all 3 HUD's working at the same time updating live for all tables on all comps in the same database?

[pr1mo]

So that would mean 2 sets of reg codes accessing the same postgres database on the main desktop comp that would act as the network host database for the HUD for all comps. Ok for 2 sets of reg codes to access the same database on the same network in this manner?

[WhiteRider]

Although importing from multiple computers / PT3 installations at the same time seems to work, it is not officially supported (i.e. not guaranteed safe) and could potentially cause problems in your database.

Once you have the reg codes I don't think there would be any problem linking more than 2 computers to the same database, but as I said above, you shouldn't import from more than one at once.

[_dave_]

I am prepared to say it will almost certainly hose a database running multiple auto-import at the same time.

For now it is much safer to have the multiple computers write their hand history files to a shared folder, and have a single PT3 auto-importing from there.

[keggler]

I am prepared to say it will almost certainly hose a database running multiple auto-import at the same time.

For now it is much safer to have the multiple computers write their hand history files to a shared folder, and have a single PT3 auto-importing from there.

doesn't seem to dave; been running 3 autoimports into the same postgres for 3 months now on my testbed; no hiccups... :D


susan