When to Create or Update SQL Table Definitions

Situation	Action
A file has not been exposed through this gateway dictionary	Import its definition once.
A new or replacement gateway dictionary has no definitions	Import the files needed by its users.
APPX fields, field order, occurrences, storage layout or key definitions change	Have the administrator review and replace the affected SQL metadata after the APPX dictionary/structure changes are complete.
Records are added, changed or deleted in an existing APPX file	Query or refresh the client; an ASQL import is not needed just to obtain current records.
Another user installs Excel, Access or the ODBC driver	Configure that desktop's DSN; do not repeat the shared import.
An Access local copy is stale	Repeat the Access data import; ASQL does not refresh that copy.

Importing changes shared SQL metadata. A generated metadata import does not copy or rewrite the native APPX records, but replacing definitions can interrupt queries, change names used by reports, or discard custom SQL edits. Treat re-import as administration rather than a routine Refresh button.

Before replacing an existing definition, preserve the gateway dictionary and any customized SQL, identify dependent reports or views, and arrange a quiet interval for the affected users. Select the individual file in ASQL. Selecting a database or application folder can apply an operation to many files.

Do not assume that every ASQL release automatically replaces an existing table. The 5.5.4 source executes generated CREATE statements and stops at a failing statement. If the existing definition causes Table/View/Synonym already exists, have the administrator perform a controlled metadata replacement, then import and verify the complete rows again. Avoid using Drop Tables on a parent folder. The historical import manual explains the need to re-import after structure changes; its automatic-replacement description should not be assumed for this package.