cancel
Showing results for 
Search instead for 
Did you mean: 

ODBC for Thick Client - does it still need to be installed locally for external auto fills to work?

angela_adams1
Champ in-the-making
Champ in-the-making

ODBC for Thick Client - does it still need to be installed locally for external auto fills to work?

1 ACCEPTED ANSWER

Jonathan_Finney
Elite Collaborator
Elite Collaborator

Hello Angela,

Thank you for posting to Community.

When using External AutoFill Keyword Sets in the Thick Client, the ODBC connection to the external database must be created on every workstation that will accessing the External AutoFill Keyword Set. This ODBC connection should also have the same name as the ODBC connection configured for the AutoFill Keyword Set (OnBase Configuration > Keyword > Keyword Types > select the keyword type > DataSet > External > DSN).

The exception to the above statement is when expanding an External AutoFill Keyword Set through a core-based product. In this scenario, the ODBC connection should be configured on the Application Server itself and not the workstations using the Core-Based product to connect. The ODBC connection on the Application Server should also have the same name as the ODBC connection specified in the External AutoFill configuration.

Thanks.

Jonathan Finney

Hyland Software Tech Support Team Leader

View answer in original post

1 REPLY 1

Jonathan_Finney
Elite Collaborator
Elite Collaborator

Hello Angela,

Thank you for posting to Community.

When using External AutoFill Keyword Sets in the Thick Client, the ODBC connection to the external database must be created on every workstation that will accessing the External AutoFill Keyword Set. This ODBC connection should also have the same name as the ODBC connection configured for the AutoFill Keyword Set (OnBase Configuration > Keyword > Keyword Types > select the keyword type > DataSet > External > DSN).

The exception to the above statement is when expanding an External AutoFill Keyword Set through a core-based product. In this scenario, the ODBC connection should be configured on the Application Server itself and not the workstations using the Core-Based product to connect. The ODBC connection on the Application Server should also have the same name as the ODBC connection specified in the External AutoFill configuration.

Thanks.

Jonathan Finney

Hyland Software Tech Support Team Leader