ODBC and JDBC Developer’s Guide
Table Of Contents
- Chapter 1 Introduction
- Chapter 2 Using ODBC to share FileMaker data
- Chapter 3 Using JDBC to share FileMaker data
- Chapter 4 Supported standards
- Appendix A Mapping FileMaker fields to ODBC data types
- Appendix B Mapping FileMaker fields to JDBC data types
- Appendix C ODBC and JDBC error messages
- Index
16 FileMaker ODBC and JDBC Developer’s Guide
For additional information, see Installing FileMaker ODBC and JDBC Client Drivers, which is available
on the FileMaker
Pro CD in the folder \xDBC\Electronic Documentation, and in the folder \English
Extras\Electronic Documentation where you installed FileMaker Server.
Configuring the ODBC client driver (Mac OS)
Configure the client driver using the ODBC Administrator bundled with the iODBC driver manager
software recommended for your client application. If you require the OpenLink ODBC Administrator, it is
bundled with the ODBC-JDBC Lite Bridge download available on the OpenLink web site.
The client driver has been tested with the following ODBC Administrators:
1 OpenLink ODBC Administrator 3.52.1 (available from OpenLink Software)
1 Apple ODBC Administrator 1.0.1 (available with Mac OS 10.3)
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 individual FileMaker database file you want to access as a data source (in previous
versions of FileMaker
Server and FileMaker Pro, you created only one DSN for all FileMaker database files
hosted by the application). The DSN identifies the FileMaker ODBC driver, the location of the 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 file 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/ivslk18.dylib
/Users/<user>/Library/ODBC /Users/<user>/Library/ODBC/SequeLink.bundle/Contents/MacOS/
ivslk18.dylib