
ODBC is a standard that allows different databases to communicate using SQL. The main reason why these features are somehow neglected is that they require a DSN (Data Source Name) to be installed at the operating system level, and sometimes, depending on the database, a specific driver.Ī DSN is needed for the operating system to give applications access to an ODBC data source. Come back to this tip after reading this article. Tip: Execute SQL can also modify the structure of a database.

One could expect that Execute SQL would return the result of a SELECT statement to a variable, but it doesn’t. Note that it is not possible, at least to my knowledge, to read data from an external source without writing to a FileMaker table (import).
#ACTUAL TECHNOLOGIES ODBC MANAGER DRIVER#
Note that on Mac, a third party driver is required (Actual Technologies). Since the release of FileMaker 15, Postgresql and DB2 have joined the game. Since FileMaker 9, we used to be able to play with mysql, Oracle and SQL Server. The purpose is here to interact with external data as if they were FileMaker data, through table occurrences, layouts, scripts…).
#ACTUAL TECHNOLOGIES ODBC MANAGER PRO#
An ODBC driver is provided with FileMaker Pro and FileMaker Server. It is not our topic today but it’s interesting because a FileMaker source interrogated via ODBC will act as any other database. FileMaker can be defined as an ODBC data source.ODBC is implemented in 3 very different manners in FileMaker. 🙂 Some technical background for a startįileMaker has had a great friend for a long time: ODBC. If you answered no to all of these, I’m jealous. Have you never lost your temper in front of a progress bar during a sync operation on a ESS table? Have you never felt anxiety before renaming a field because it could break an import order? Have you never cursed the SQL developer who uses as a unicity key a concatenation of several columns? Have you never been bothered by inconsistent database structures between a data source and your own application? (Note: If you're using Leopard, clicking on the ODBC keywords and values can be a little difficult to edit them.In this blog post, I will share a technique that Laurent Spielmann ( and I developed together and that greatly simplifies imports. Now the important bit, you need to create 5 Keyword-Value pairs as below, click on the Add button at the bottom left to add each set.Optional: fill in some text in the description field.Two notes here, 1) it doesn't need to be the same as the name of the database itself 2) just to err on the side of caution, I'm entering in all the data lower case, no spaces or special characters. So in the DSN box, enter in a unique name for the database that you want to refer to it by. The DSN identifies the FileMaker ODBC client driver, the location of the FileMaker host application, and the FileMaker database file you’re accessing as a data source. Here's the relevant blurb from the Filemaker Documentation: You need to create a DSN for each FileMaker database file you want to access as a data source. Another screen will appear asking you to set a Data Source Name (DSN).Select the driver, in my case FilemakerProUser and click OK. You'll get a drop down come up where you need to select the driver you just installed above.If not, then let me know what is the error message, and we'll proceed from there.


This should return everything was successful. Click on the System DSN tab, and click the "Add" button.ġ1. I clicked "Add a driver", and entered the following information:ĭriver file name: /Library/ODBC/SequeLink.bundle/Contents/MacOS/ivslk20.dylib I launched iODBC Administrator and selected the tab "ODBC Drivers".Ĩ. I turned on ODBC Sharing, selected "Test.fp7" in the lower left, and set ODBC/JDBC access to "All Users", and clicked "OK".ħ. I pulled down the File menu and selected "Sharing -> ODBC/JDBC."Ħ. I launched FileMaker Pro 10, created a new database file "Test.fp7" with one field (Name) and one record (TSGal)ĥ. I put in my FileMaker Pro 10 disc, opened the xDBC directory and copied the SequeLink.bundle into the Hard Drive -> Library -> ODBC (folder)Ĥ. I installed it, and it was placed inside my Hard Drive -> Applications -> iODBC (folder)ģ. I downloaded the iODBC Administrator at:Ģ.
