How to use ODBC and Dentrix 11 to G4.
The Dentrix ODBC Driver seems to want SQLExecDirect for a SELECT call, and the driver wants the first 4 characters to be XOR encrypted with the first character appended to the front that is part of the one time pad or key. I suspect this key is similar to Dentrix G5 and G6 on the guid to password algorithm. The G5 key I figured out, the G6 algorithm is stronger, and I haven't really looked at trying to break it. Besides, there are other ways.
Another project is Driller but it does not use the ODBC Driver and instead sticks the data into a MySQL database. More on that at a later time, though it is on google.
ODBC allows you to see the Dentrix Data without using the Letters feature in Dentrix.
Be sure to disable UAC or run these programs in an elevated environment.
Set the Dentrix Data Directory in the ODBC Driver
![]()
I used Advanced Query Tool 10.1 to extract data from tables using the SQL Interface:
Set some options, Use SQLExecDirect
![]()
![]()
![]()
![]()
Credit goes to TwoBitsShort
The Dentrix ODBC Driver seems to want SQLExecDirect for a SELECT call, and the driver wants the first 4 characters to be XOR encrypted with the first character appended to the front that is part of the one time pad or key. I suspect this key is similar to Dentrix G5 and G6 on the guid to password algorithm. The G5 key I figured out, the G6 algorithm is stronger, and I haven't really looked at trying to break it. Besides, there are other ways.
Another project is Driller but it does not use the ODBC Driver and instead sticks the data into a MySQL database. More on that at a later time, though it is on google.
ODBC allows you to see the Dentrix Data without using the Letters feature in Dentrix.
Be sure to disable UAC or run these programs in an elevated environment.
Set the Dentrix Data Directory in the ODBC Driver
I used Advanced Query Tool 10.1 to extract data from tables using the SQL Interface:
Set some options, Use SQLExecDirect
2AW^WCT = SELECT
aSTI_RT = INSERT
You can get more with enabling the ODBC Tracing Log in Windows.
SQL Query Tool 6.1 works just fine without setting any options. Seems it works without SQLExecDirectW (this program uses SQLExecDirect)
Credit goes to TwoBitsShort