During my time of developing databases since version 2.x (now this is going back some years), I have found FileMaker Pro to be an excellent application primarily for the ease in which databases can be created and the flexibility and useful features it provided.
However, since FileMaker Pro 10, I have noticed certain unwelcomed changes. For a start, there are instability issues. We have lost Instant Web Publishing (IWP) in FileMaker Pro 13. And the security of data in fields of any table is now compromised due to a security hole placed into the Data Viewer feature since version 10.
Of greatest concern are the following issues I have noted with FileMaker Pro 13 and confirmed by other developers:
1. FileMaker Support pages show a question from a developer titled "FileMaker Go - Calculations involving GetNthRecord fail after 29 records" and a response suggesting FileMaker Inc is aware of the issue since 10 April 2013. Whether the issue has been fixed in FileMaker Go 12, I observe in FileMaker Pro 13 Advanced that the issue remains and actually fails to show the calculation result from the 79th record onwards. This is a major problem for my clients in terms of financial information they need to work with in the databases. So, on checking this with FileMaker Pro 12 Advanced I see the issue does not exist. It is only FileMaker Pro 13 that has introduced the bug since the last version (perhaps the bug was ported over from FileMaker Go 11), Since April 2013, the issue has not been fixed properly across the full FileMaker Pro 13 product range by checking that the GetNthRecord function works properly.
2. I note from the FileMaker Forum a developer wrote in February 2012 under the title "SECURITY ISSUE: Can't Hide Data Viewer from User's..." how the data viewer allows any user with a copy of Advanced app to view data in any field of any table in any non-admin/developer login account. Prior to FileMaker 10 the data viewer button for selecting fields to view data would be greyed out (unless you are actually logged into the developer account to modify the database). This is no longer the case and, in fact, FileMaker's recommendation is to request that users do not use the FileMaker Pro Advanced app. Unfortunately I cannot monitor this with my clients and, therefore, consider this a major security flaw in the product. I concur with the other developer. And now I see the issue has not been fixed since I mentioned this with FileMaker Inc in December 2012 (in writing). All that FileMaker Inc will do is force developers to use the new database file encryption option. However this new feature places an unnecessary burden on my clients by introducing another level of authentication and to further compromise the intellectual property of my solutions when I cannot remove the admin account with Runtime solutions just to satisfy the encryption requirements.
3. A serious bug existed when working in scripts causing sudden and unexpected quits (especially in FileMaker Pro 12). While I lived with this problem (the essential scripts were in place and I can minimise the crashes if I don't do too much work in modifying scripts), I see the latest FileMaker Pro 13 may have addressed this issue. However, the bug seems to have been moved over to the launch sequence when starting up a database. It doesn't happen all the time (so far about a dozen times for myself since I purchased FileMaker Pro 13 Advanced). It also occurs when you are in a text field for more than 15 minutes doing changes to the text and you don’t save the text by committing the record. As a result, time is wasted waiting for the FileMaker Pro app to check the integrity of the databases. Furthermore my clients feel concerned about the possibility that such unexpected quits may cause irreversible damage to the databases should the problem persist over a period of time. Prior to FileMaker Pro 12, I have not seen this level of serious bugs crashing the app so easily. Now I understand my clients concerns and feel FileMaker Pro 13 is not up to scratch for prime time use in real world database solution environments.
After noticing these issues and explaining them to FileMaker Inc and requesting these issues by fixed as quickly as possible, the company has agreed instead to provide a refund for FileMaker Pro 13 (i.e. within the 30 days of purchasing the product). I sense the company may not be interested in fixing these issues with the potential that Apple could be trying to drop further development work of FileMaker Pro in the near future. Why? Apple does not like consumers to get free or low-cost FileMaker contacts databases to bypass the company’s own contacts.app for identifying users and sending personal details to the iCloud. FileMaker Pro should only be used for large organisations and not for individual consumer use.
Given how long the company has been notified of the above issues, this appears to be the case.
I do note that numerous FIleMaker developers have complained in the past about how each upgrade of FileMaker under the control of Apple has only provided few extra features, but not substantial enough to be considered good value for money.
I just wonder whether Apple/FileMaker Inc is serious about its commitment to providing a good product to the consumer?
But if this isn’t the case, I strongly recommend you check your FileMaker Pro 13 product very carefully. If it works for you, fine. If it doesn’t, get a refund. The more people who get refunds, the more likely FileMaker Inc will make efforts to fix bugs and provide a quality product to the consumer.