Chapter 2: Install and Check APPX ODBC
Check the Saved AppxODBC Connection (DSN)
Use the default dictionary
The gateway installer creates the appx SQL dictionary and writes the APPX server endpoint to appx.dbs\appx.env. Use that default dictionary. No additional mdcreate command is required for this recipe.
The default names refer to different things:
| Name | Purpose |
|---|---|
appx | SQL dictionary on the gateway |
AppxODBC | ODBC data source on the Windows client |
DMO / DMO | Database ID and Application ID inside APPX |
On an existing test installation, preserve the current DSN before replacing it under the same AppxODBC name. Keep the existing appx dictionary and import COUNTRY into it with ASQL.
Check the client driver and DSN
Leaving the ODBC Service field blank is valid for the standard connection. Blank uses the default sqlnw TCP-name lookup; entering sqlnw explicitly uses that same lookup. Leave Service empty for this recipe, as in the current login screenshots. The supplied driver installer omits this optional value; entering sqlnw is an explicit alternative. Keep Database appx: it selects the SQL dictionary and does not belong in Service. With either blank or explicit sqlnw, verify that the client's mapping reaches this gateway on TCP 1992. Read Service, its blank default and custom aliases before changing the field.
Complete Install the 6.2.1 Client Driver first. It creates or updates AppxODBC while preserving the default dictionary. Then check the gateway port mapping and the data source below.
- On the client computer, back up
C:\Windows\System32\drivers\etc\servicesand ensure that thesqlnwmapping resolves to the verified gateway port. For this cookbook the mapping is:
sqlnw 1992/tcp
Resolve duplicate or conflicting sqlnw entries before proceeding. Leave the ODBC Service field blank for this recipe. Entering the TCP alias sqlnw explicitly is also valid. Both use this mapping to reach TCP 1992; neither starts the gateway or changes its listener. Use a different named alias only for a deliberately configured alternate port. How the services file and fallback work.
- Open
C:\Windows\SysWOW64\odbcad32.exeand check System DSN forAppxODBC. This is the 32-bit ODBC Administrator. The program in System32 manages 64-bit drivers.
Next, import the COUNTRY metadata with ASQL. An empty dictionary cannot answer the sample queries until that import completes.