Hi Stu,
I'm not actually by-passing the dialogue, once the scanner data is received it invokes an event to automate navigation through the various TD prompts.
The scanner transmits the barcode number which is associated with each "player ID" in TD. The code is captured by a program called T-wedge and passed to TD as keystrokes. In addition to passing the barcode number, I can use T-wedge to add whatever else I need to perform the registration and bust-out tasks. T-wedge includes Java Script capabilities, so basically I can instruct the application to pass specific TD hotkeys to enter buy-in or bust out dialogues, I can pass "tab", "space" and "enter" keystrokes to navigate around the dialogues, and I can enter delays to wait for IE print tasks, etc. I can also transmit characters to the scanner to achieve various tasks, like disabling the scanner temporarily if I have an extended TD event which needs to complete.
Hope this helps
Beaker