Using FireDAC
Go Up to Multi-Device Development (FireDAC)
Generalities
For multi-device development, FireDAC supports the following platforms:
- Windows
 - macOS
 - iOS
 - Android
 - 64-bit Linux
 
In general, FireDAC application development for macOS, iOS, Android and Linux is similar to that for Windows, but there are several different aspects:
- The GUIx components must have Provider = 'FMX' to use FireMonkey, or 'Console' to use console implementation for FireDAC GUI components. Note that switching to Provider = 'FMX' or 'Console' may require you to delete FireDAC.VCLUI.Xxx units from the "uses" clauses.
 - Try to avoid specifying design-time paths for FireDAC properties, such as TFDPhysDriverLink.VendorLib or TFDCustomManager.ConnectionDefFileName. Use default values, FireDAC configuration files or path variables.
 - An application and a DBMS client dynamic library bitness must be the same. x86 executable uses x86 libraries. x64 executable uses x64 libraries.
 - On macOS and Linux, the ODBC-based drivers (SQL Server, IBM DB2, SQL Anywhere) may require explicit ODBC driver specification, using the TFDPhysXxxxDriverLink.ODBCDriver property or configuration file.
 - The Microsoft Access driver is supported only on Windows platforms.
 
- The Microsoft SQL Server ODBC driver and FreeTDS ODBC driver have a quite different behavior and quality.
 - The SQLite driver supports static linking only for Win32 and Win64. For other platforms, the dynamic libraries must be provided.
 - The Informix driver is not supported on Linux.
 - Utilities are provided for Windows only.
 
Configuring FireDAC
The following steps are required in order to use persistent connection definitions or virtual drivers, shared by several applications:
- Go to 
C:\Users\Public\Documents\Embarcadero\Studio\FireDAC - Drag FDConnectionDefs.ini and drop it to your project (in the Projects Window).
 - Click the Yes button to add it to your project.
 - Drag FDDrivers.ini and drop it to your project (in the Projects Window).
- Note: This file is optional.
 
 - Click the Yes button to add it to your project.
 - Open the Deployment Manager (go to Project > Deployment).
 - Set the Remote Path of the selected target:
- For macOS platform: Contents\MACOS
 - For iOS platforms: StartUp\Documents
 - For Android platform: assets\internal