MariaDB 10.11 with APPX 5.5.4 on Windows
Set up MariaDB as an APPX file system using FMS type 6. Start with one file, then save a record in APPX and check it in MariaDB.
APPX 5.5.4 · 32-bit engine MariaDB 10.11 · MariaDB Connector/ODBCWhat to install
The example uses a 32-bit APPX 5.5.4 engine on Windows 11 25H2 and a 64-bit MariaDB 10.11.18 database. Install the 32-bit MariaDB Connector/ODBC client on the APPX server.
| Component | Download |
|---|---|
| APPX server | Install the 32-bit APPX 5.5.4 engine and set up an APPX Login Manager. APPX 5.5.4 Windows server installer · Installation instructions |
| APPX Desktop Client | Use the 5.5.4 Desktop Client to open an APPX session. Desktop Client installer |
| MariaDB | Install MariaDB 10.11 or use an existing server with a dedicated test database. Database installation |
| ODBC driver | Match the client to the APPX engine’s 32-bit architecture. MariaDB Connector/ODBC 3.1.22 |
Choose a database and create a login
Ask your DBA for the host, port, and database name. This single-byte example uses appxsb with latin1_general_ci. Use a dedicated schema or database to rehearse the setup. Replace the example password with a generated value.
CREATE DATABASE appxsb
CHARACTER SET latin1 COLLATE latin1_general_ci;
CREATE USER 'appx_maria_demo'@'127.0.0.1'
IDENTIFIED BY 'use_your_test_password';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, INDEX, DROP
ON appxsb.* TO 'appx_maria_demo'@'127.0.0.1';
Set up the 32-bit System DSN
On the APPX server, run %windir%\SysWOW64\odbcad32.exe as an administrator. Select System DSN → Add and choose MariaDB Connector/ODBC. Set the DSN name to APPX-MARIADB, host to 127.0.0.1, standard port to 3306, and database to appxsb.
Set the connection character set to latin1. Test using appx_maria_demo. APPX supplies the password from the FMS identity.
A newer version of MariaDB ODBC Driver is already installed. If the 3.1.22 x86 MSI reports this message, save the signed win32.msi package and extract it as an administrator. Set $msi to the downloaded package path.
$dest = 'C:\Appx\mariadb-odbc-x86'
Get-AuthenticodeSignature $msi
When the signature status is Valid and the signer is MariaDB, extract the package.
$msiArguments = "/a ""$msi"" /qn TARGETDIR=""$dest"""
$install = Start-Process msiexec.exe -ArgumentList $msiArguments -Wait -PassThru
$install.ExitCode
Confirm an exit code of 0. If the setup dialog cannot create a DSN, use the extracted driver to register a new x86 System DSN. Use a DSN name available for this test and set the server and port for your test database.
$driver = Get-ChildItem $dest -Filter maodbc.dll -Recurse |
Select-Object -First 1
$name = 'MariaDB ODBC 3.1 Driver (APPX x86)'
$reg = [Microsoft.Win32.RegistryKey]::OpenBaseKey('LocalMachine','Registry32')
$inst = 'SOFTWARE\ODBC\ODBCINST.INI\'
$key = $reg.CreateSubKey($inst + $name)
$key.SetValue('Driver', $driver.FullName)
$key.SetValue('Setup', (Join-Path $driver.DirectoryName 'maodbcs.dll'))
$key.SetValue('APILevel', '2')
$key.SetValue('ConnectFunctions', 'YYY')
$key.SetValue('DriverODBCVer', '03.51')
$key.SetValue('FileUsage', '0')
$key.SetValue('SQLLevel', '1')
$reg.CreateSubKey($inst + 'ODBC Drivers').SetValue($name, 'Installed')
$ini = 'SOFTWARE\ODBC\ODBC.INI\'
$dsn = 'APPX-MARIADB'
$data = $reg.CreateSubKey($ini + $dsn)
$data.SetValue('Driver', $driver.FullName)
$data.SetValue('SERVER', '127.0.0.1')
$data.SetValue('PORT', '3306')
$data.SetValue('DATABASE', 'appxsb')
$data.SetValue('CHARSET', 'latin1')
$reg.CreateSubKey($ini + 'ODBC Data Sources').SetValue($dsn, $name)
Open the 32-bit ODBC Administrator and confirm the System DSN. Use the same name in APPX.
Set up the FMS group and identity
Open a new APPX Desktop Client session. Choose System Administration → Configuration → File System Groups under File Maintenance.
- Add
APPX-MARIADBand enter FMS type6. - Click FMS Group Attributes. Enter the values below and save.
| FMS option | Value |
|---|---|
| Data Source Name | APPX-MARIADB |
| Table Naming Scheme | APPX_$db_$appl_$file |
| Proxy Database ID | LOK |
On the group row, click Identities. Enter your APPX user ID to give that user a database login. Leave APPX User blank to set a default identity for the group. Press Enter to accept the key and again to open the details.
Enter appx_maria_demo in User Id and leave Realm blank. Save the identity and reopen it in Change mode. Click Change Password, enter the database password, and press Tab to move to Confirm Password. Enter it again and click Change Password. When APPX reports Password Changed, END to Exit, close the password dialog and save the identity. Open a fresh APPX session before testing.
Assign one file and create the table
Use a test database and a file you can create empty. This example uses the Demo Application’s COUNTRY file.
- Open System Administration → Database/Applications → Databases / Applications under File Maintenance. Add
TSTwith the company name MariaDB Test. Set the startup application toDMO, version00. Save and accept the report defaults. - For
TST, open Related Applications. AddDMOin Live Operations if it is absent. Select theDMOrow and click Database Management. If APPX prompts for a Language ID, setENGand reopen Database Management. - In File Selection, click Unselect All. Highlight
COUNTRYand press F3. If you use the Select button, enterCOUNTRYin Name and confirm. Return to Data File Management and confirm that one file is selected. - Open File Specifications. Set FMS to
6and FMS Group toAPPX-MARIADBforCOUNTRY. Save and return. - Choose Create Files. The result for
COUNTRYshould say Created.
This naming scheme creates APPX_TST_DMO_COUNTRY in the selected database or schema. For an existing file, follow the APPX/IO migration and rollback guide.
Save and check a record
- From the APPX main menu, choose Run an Application and execute database
TST. In the demo’s top menu, choose Setup → Countries. - In Country Address Format Rules, choose Add. Enter
CANADAfor Country Name,PROVINCEfor Region Label, and2for # Words In Postal Code. Leave Postal Code Location at AFTER REGION. Click Save. - Repeat with
ENCODINGfor Country Name,Québecfor Region Label, and1for # Words In Postal Code. Save. - Open a fresh Desktop Client session, run
TST, and go back to Setup → Countries. Choose Inquire and click First Record if the key field is empty. Find the two keys and confirm the saved values, including the accent inQuébec.
Cannot Access Required File for PROSPECT. In a test database with only COUNTRY created, click Cancel on this message to continue the Countries test. Create the full demo database to run the rest of the application.
Connect independently in mariadb as appx_maria_demo. Check the records, encoded value, and unique index on country_name.
SELECT RTRIM(country_name), RTRIM(country_region_label), country_no_words,
HEX(RTRIM(country_region_label)) AS stored_bytes
FROM APPX_TST_DMO_COUNTRY ORDER BY country_name;
SHOW INDEX FROM APPX_TST_DMO_COUNTRY;
Expect CANADA / PROVINCE / 2 and ENCODING / Québec / 1. In the Windows-1252 text, é is byte E9.
Troubleshooting
Check the APPX engine
This guide uses FMS type 6 (ODBC) through the MariaDB ODBC driver.
In APPX Release Information, record Engine Release and Compile Date. The application release numbers on the same screen identify the APPX system applications. Match the database client or ODBC driver to the bitness of the engine that runs the operation. Check the settings on the APPX server and under the Windows or Linux account that runs the engine.
Test the connection outside APPX
On the APPX server, open the 32-bit ODBC Administrator (%windir%\SysWOW64\odbcad32.exe on 64-bit Windows). Under System DSN, open the DSN from FMS Group Attributes. Confirm the driver, server, port, and database. Run Test with the same login and password as APPX. Close the setup dialog with Cancel if you entered credentials just for the test.
For a timeout or connection refusal, check the database service, listening address and port, and firewall. A database authentication error means the request reached the server. Check the matching server log entry for the reason it rejected the login.
For Access denied, check the user and client host in the error. MariaDB matches accounts by user and host.
Check the FMS group and Identity
If APPX reports Can’t connect to server (or driver error) after a successful DSN test, confirm that the FMS group’s Data Source Name matches the tested System DSN. The DSN test uses the credentials supplied to the test. APPX uses the credentials from its FMS Identity.
Under Identities, look for an active, unexpired entry for the APPX user running the operation. That entry takes precedence over the blank default. Check User Id and re-enter the database password with Change Password. Save the Identity and open a fresh APPX session. APPX can cache connection and Identity settings for the life of the session.
If the same password works in the DSN test and fails in APPX, check the driver’s connection string rules and the password length supported by the APPX release. A dedicated test login with a newly generated alphanumeric password can help isolate a parsing or length problem.
Check where APPX creates the table
If the connection succeeds, read the Create Files result or open View Log for the database error. Check the database, login, and target schema or database with the same connection settings as APPX. Compare the APPX database ID, application ID, file name, and Table Naming Scheme with the SQL table name.
In the MariaDB client, run SELECT DATABASE(), CURRENT_USER(); and SHOW GRANTS;. Check CREATE on the selected database. Use SHOW TABLES; to check the exact spelling since table name case can differ by platform.
For a proxy file error, check the FMS group’s Proxy Database ID (LOK in this example) and the engine account’s access to the proxy files under APPXPATH. If APPX reports that a record is held, check whether another APPX session has it open in Change mode.
Capture one failing operation
Make a copy of the
appx.envunder the effectiveAPPXPATHof the engine that runs the process. Create a private log directory that the engine account can write to, then temporarily set the variables below. Keep$(pid)as written. The SQL logger replaces it with the engine process ID.APPX_SQL_CMD=C:\APPX\Logs\appx-rdbms-$(pid).log APPX_DBG_CODE=0x201FThe mask includes generated SQL, return statuses, fetch attempts, and engine and connection operations, plus proxy lock operations where applicable. Use
0xFFFFFFFFfor one attempt if support needs more detail. The engine reads these settings on startup.APPX_ODBC_LOGandAPPX_ODBC_CODEapply to the driver used by external programs to read APPX data.- If the APPX SQL log lacks the driver error, open Tracing in the same 32-bit ODBC Administrator. Set Log File Path to a private file the engine can write, such as
C:\APPX\Logs\odbc.log. Click Apply, then Start Tracing Now. If tracing must include an engine running under another Windows identity, use Machine-Wide tracing for all user identities for this attempt. Windows ODBC tracing - Open a fresh APPX session and reproduce the failure once. For Create Files, select only the intended test file. For a failed
READwithHOLD, note the APPX error and flags before the nextWRITE. Try a plainREADof the same key in another fresh session. If the log is missing, checkAPPXPATH, the effective variables, and the engine account’s access to the log directory. - Exit the test sessions and restore the previous
appx.envsettings. If you enabled ODBC tracing, click Stop Tracing Now and restore the previous tracing options.
If an insert follows a failed held read, keep the first error. A later duplicate-key error indicates that the key existed when the insert ran. Use the insert branch only when the read explicitly reports that the record was absent. Handle lock and database errors before trying another write.
In the ODBC trace, find the first failed call and its diagnostic records. For SQLDriverConnect (which may appear as SQLDriverConnectW), capture the return code, SQLSTATE, and full driver message. IM002 points to DSN or driver lookup. 08001 covers several connection failures, so read the message that accompanies it.
Share the SQL statement, fetch or lock result, and the first SQLSTATE, native error number, and message when available. Include the APPX flags, file and operation, timestamp and time zone, APPX engine release, build date and bitness, operating system, driver name and version, and database versions before and after an upgrade. Keep the SQL structure and error codes intact and replace passwords and record values with placeholders. The APPX SQL log can contain the engine environment and full connection strings. APPX environment settings
If the SQL query returns a different result from the APPX screen, verify the effective FMS group, database, schema, and table name. Restart the APPX session after changing any of them.