ODBC and JDBC Guide

Chapter 3
|
Using ODBC to share FileMaker data 19
5. Click Test Connect.
You are prompted to enter your FileMaker account name (in Database User Name) and password (in
Database Password).
If the connection is OK, you’ll receive the message Connection test was successful. If the connection fails:
1 Make sure the FileMaker database file is hosted and available.
1 Update or correct your connection information.
1 Make sure your FileMaker account uses a privilege set with the extended privilege of Access via ODBC/
JDBC.
1 Verify that the FileMaker Pro or FileMaker Server host application has been set up for sharing via
ODBC/JDBC.
Accessing a FileMaker database file from a Mac OS application
If you build custom applications, use version 3.52.1 of the ODBC headers and libraries. Applications built
with version 3.51 might not be able to load the client driver.
Configuring the ODBC client driver (Mac OS)
Configure the client driver using the ODBC Administrator bundled with the ODBC driver manager software
recommended for your client application.
This client driver has been tested with ODBC Administrator 1.0.2 (available with Mac OS 10.4.11) and
ODBC Administrator 1.1 (available with Mac
OS 10.5.4).
When configuring the client driver, you’ll be prompted to provide a brief description and the path to the
driver file:
The ODBC Administrator also allows you to optionally define keywords and a Setup File path, but the client
driver does not need that information.
Specifying ODBC client driver properties for a FileMaker DSN (Mac OS)
Create a DSN for each FileMaker database file you want to access as a data source. 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.
Important The ODBC client driver for Mac OS does not support upper-ASCII, double-byte, or Japanese
characters in database names or table names. If your FileMaker database file uses these characters, create a
second database and use only ASCII characters for the filename and table names. In the second database,
create a data source reference that points to the data in your original database file. Share both files with
ODBC/JDBC, but use the second database file when defining the DSN.
If you copied SequeLink.bundle
to this library: Use this driver path during configuration:
/Library/ODBC /Library/ODBC/SequeLink.bundle/Contents/MacOS/ivslk20.dylib
/Users/<user>/Library/ODBC /Users/<user>/Library/ODBC/SequeLink.bundle/Contents/MacOS/ivslk20.dylib