ODBC access in the 6.2.1 test | APPX Data File Encryption

APPX 6.2.1 successfully read the encrypted native COUNTRY file through ODBC in this test. The configuration used the 64-bit Windows APPX 6.2.1.0 engine, matching 6.2.1.0 gateway, supplied 64-bit Dharma 14.01 driver, and 64-bit Windows PowerShell 5.1. COUNTRY was a native format-3 file with eight records and nine SQL columns. The test ran in an isolated VM with its network adapter disconnected.

The queries were:

SELECT COUNT(*) AS country_count FROM DMO_DMO_COUNTRY;
SELECT * FROM DMO_DMO_COUNTRY ORDER BY no_words, name;
SELECT no_words FROM DMO_DMO_COUNTRY ORDER BY no_words;

Check	Result
Unencrypted controls with a fresh gateway for each case	All three queries passed
Native APPX export while encrypted	A newly created CSV matched the original byte for byte; the physical ENCRYPTED flag was present
ODBC while encrypted	Count returned 8; the full-row query returned all eight rows and nine columns; all 72 returned values matched the ODBC baseline
After decryption	All three queries passed; returned values and the new native CSV matched their baselines
Unique value after re-encryption and restart	ODBC returned the expected numeric value 7 and audit value JPN from the encrypted file

For the final proof, Canada's no_words value was changed from 2 to 7 through APPX CSV Replace in the disposable test copy. A native export confirmed the change while the file remained encrypted. After a clean VM restart and another physical encryption check, this fresh ODBC query returned exactly one row containing 7 and JPN:

SELECT no_words, added_by FROM DMO_DMO_COUNTRY WHERE no_words = 7;

The original test data contained no no_words value of 7. This extra check established that ODBC read the marked encrypted file. Use a suitable unique value for your own test dictionary and data.

The test also encountered intermittent connection-setup stalls before SQL execution, including with encryption disabled. Fresh unencrypted controls and the marker query after restart succeeded. If connection setup stalls at your site, resolve that separately and repeat the check with fresh connections.

Check complete text values against native APPX. The tested ODBC configuration truncated some text even with encryption disabled; encryption and decryption did not change that behavior. Matching ODBC outputs across encryption states alone do not establish correct character handling. The numeric and audit marker values above matched their native values.