fiiop.blogg.se

On macOS, FileMaker Pro requires the Actual Technologies Open Databases ODBC driver.

On Windows, FileMaker Pro requires the official MySQL driver, the MySQL Connector\ODBC (currently, the best option is Connector\ODBC 5.1.13). The CData MySQL Remoting daemon (included with the driver).This article shows how to link each of the following components with FileMaker Pro: Compared to a native ODBC integration, FileMaker Pro integrations that use MySQL remoting have several additional components. The JDBC driver is part of a data access chain. The remote data can be modified in FileMaker Pro and tables can be used in the relationships graph like standard FileMaker Pro tables. To use this approach, see ODBC GraphQL Integration in FileMaker Pro.ĮSS: Instead of working with a local copy of the data, you can use the JDBC driver to create an external SQL source. To streamline this solution, use the CData ODBC driver, as FileMaker Pro supports ODBC natively, but it does not support JDBC. There are two data access modes in FileMaker Pro:ĭata Import: GraphQL data is copied into a FileMaker Pro database and can be refreshed on demand. The CData JDBC Driver for GraphQL implements both the JDBC and MySQL standards to integrate with applications like FileMaker Pro that support connections to traditional databases like MySQL but not generic JDBC connections. You will use the MySQL Remoting feature to access GraphQL as a remote MySQL database. This article shows how to use the CData JDBC Driver for GraphQL to integrate with the External SQL Sources (ESS) feature in FileMaker Pro, which allows you to link records in FileMaker Pro with related records in your other operational data stores.