What do you like best?
It is really easy to create a gorgeous layout for a database. Abundant tools allow changes in position, size, color, and function. Also, it is possible, with an experienced developer, to make fluid, responsive layouts that acts as relational databases, integrating data from a variety of sources.
What do you dislike?
However, after you've created a layout, it's quite tricky to set up a relationship to other layouts. It's taken me years to get reasonably good at doing this. The FileMaker website seems to indicate that relationships should be intuitive, but they're not. Also, we use FileMaker server to allow staff to login remotely to come to work. However, we've discovered that, since we use SQL databases (via ODBC), network lag increases dramatically with increases physical location from the server.
Recommendations to others considering the product
It is difficult to find developers to take FileMaker databases beyond simple one-layout databases, at least in Canada on the west coast. There are only a handful of developers there, and therefore, with little competition, you have to take what you get.
What business problems are you solving with the product? What benefits have you realized?
We use FileMaker as a staff interface to our contacts and invoices, as well as to interface with SQL databases that drive our websites. With our staff mostly coming to work remotely, the use of FileMaker Server allows them to see the same interface, regardless of where they are.