Chapter 3: Make APPX Files Available to SQL
Show Only the APPX Application You Need
For the COUNTRY recipe, enter DMO as both Database ID and Application ID before connecting. These optional fields restrict the definitions ASQL discovers. They are distinct from the gateway's appx SQL dictionary and the Windows AppxODBC data source.
| Login fields | Definitions requested |
|---|---|
| Database DMO, Application DMO | The DMO application's files in database DMO |
| Database DMO, Application blank | Applications available within database DMO |
| Database blank, Application DMO | Matching DMO application entries across available databases |
| Both blank | The available System Directory entries across databases and applications |
In the reviewed 5.5.2 source, ASQL prepares a System Directory query based on these fields, fetches its results into a list, and then builds the tree. Leaving both fields blank requests the whole available list. Expanding a folder afterward is not the same as issuing a narrowly filtered first discovery query. Start with known IDs for a focused import, especially on an installation containing many applications or files.
If the window remains at Query dictionary... or Fetching results..., record the stage and elapsed time. Check a fresh small SQL query, reconnect with the known database/application IDs, and compare the result. This source review explains the larger query scope; it does not establish a measured network latency cause or a universal timeout. Keep a slow-discovery investigation separate from changing business-file metadata.
Do not repeatedly choose an application or database folder's Import Tables command just to make the tree appear. Discovery lists available definitions; import changes the shared gateway dictionary. Follow the individual COUNTRY import once discovery completes.