Check ODBC access before converting a file

Use a separate APPX 6.2.1 test copy. COUNTRY is convenient because the APPX ODBC cookbook imports its definition as DMO_DMO_COUNTRY. The 6.2.1 test had eight records and nine SQL columns. Your data and counts may differ.

1. With COUNTRY unencrypted and ODBC working, run the three queries below. Save all returned values, including every column of the full-file query. Close the client connections.
2. Back up the file pair, matching structures, and administration configuration. Export COUNTRY through APPX and preserve the complete CSV.
3. Follow Set the file key and replace the file, substituting COUNTRY for PROSPECT and using a new file key. Select only COUNTRY. Use no inherited group key for this independent test.
4. Confirm the physical ENCRYPTED flag on a complete working copy as described in Analyze a working copy. Export the encrypted file through APPX and compare the complete CSV with the original.
5. Open a fresh ODBC connection using the same DSN and login. Repeat the three queries. Record errors or a failure to finish, as well as successful results. Compare complete values rather than relying only on COUNT.
6. Close the test connections. Complete the file decryption procedure, again substituting COUNTRY. Confirm that the physical encryption flag is absent, then open a fresh ODBC connection and repeat the queries for the final control.

SELECT COUNT(*) AS country_count FROM DMO_DMO_COUNTRY;
SELECT * FROM DMO_DMO_COUNTRY ORDER BY name;
SELECT name, no_words FROM DMO_DMO_COUNTRY WHERE name = 'Canada';

Compare complete query results with both the saved ODBC baseline and the native APPX export. Close and reopen connections between states so the check reads the current file. Resolve connection or character-handling problems before relying on client output.