Share FileMaker Data in the Microsoft SharePoint Cloud - First Steps
You need FileMaker and XDBC installed and configured. Please download here.
FileMaker Pro for Windows to install.
You can use a Starter Solution template to jump-start your FileMaker database
project. We have selected the Contacts sample to connect to a SharePoint contact
list later on, just as a sample.
Fig.: Select a sample template to jump-start your FileMaker project.
Please import some test data entries or create manually.
Fig.: Sample contact data to sync with a SharePoint or Office 365 contact list.
As a next step we have to connect to this FileMaker database via ODBC. Please
make sure that the ODBC driver is installed. You can download here.
Fig.: Download and install FileMaker
Please note that you have to use 32-Bit xDBC. 64-Bit is available, but does not
work as expected. You will find the 32-Bit version here:
Please use the 32-Bit version of FileMaker xDBC to connect to SharePoint.
Now we can configure the ODBC connection. We have to use the Windows
ODBC Connection Manager. In case you are on 64-Bit already, you will find it in
the Windows\SysWOW64 directory (see below). Otherwise you will find in the
Fig.: The 32-bit ODBC Manager is
hidden in the SysWOW64 folder on 64-Bit systems.
Fig.: After installation you will
find the FileMaker ODBC driver listed in the ODBC Manager 32-Bit.
Please be sure to share your database for use with ODBC/JDBC. You have to
specify a certain user, otherwise it will not work as expected.
Fig.: Share your FileMaker database via ODBC to connect to SharePoint or Office 365.
Now you can connect to ODBC and create a System-DSN. Please note
that a System-DSN is required, no User- or File DSN. In this sample we call the connection myFilemaker. Please verify the connection
in the ODBC Manager. You will be promted for user (required)
and password (optional).
Fig.: FileMaker System-DSN defined
in the ODBC Manager
Now we are well prepared to connect
to SharePoint, Office 365 (or almost any other data source, e.g. SQL) via the
Layer2 Cloud Connector.