Skip to main content

FileMaker 13 has arrived

FileMaker 13 was released today (December 2, 2013). There are new versions of all the products in the FileMaker product line:

  • FileMaker Pro and FileMaker Pro Advanced
  • Filemaker Server
  • FileMaker Go for iOS
Much more can be found on FileMaker's website.

One bit of good news: FileMaker Pro 13 uses .fmp12 file format that was introduced with the previous version, so if you have some computers on your network using a FileMaker 12 database and you need to add a seat, you can buy a copy of FileMaker 13 and just add it to the mix. You won't have to upgrade everybody immediately.

But you may want to. I've been working with version 13 for a while as I work on a forthcoming review, and it seems a solid and impressive upgrade. I'll have much more info after my review is released. In the meantime, clients of Rucksack (or Polytrope) who have a question, should feel free to contact me directly.

Comments

Popular posts from this blog

Setting up OAUTH with Google in FileMaker 16

Setting up OAuth with Google in FileMaker 16 Posted by William Porter Intended audience: Intermediate to Advanced FileMaker developers Date of publication: 2017-June-06 Updated: 2018-June-06 One of the many exciting features in FileMaker 16 (released May 2017) is OAuth or Open Authentication. Open Authentication allows users to connect to a FileMaker database after authenticating with an external (non-FileMaker) account. At the present time, FileMaker supports OAuth through Google, Amazon and Microsoft. If you're a developer there are two main questions to answer. First, should I do this? And second, how do I do it? I'll answer the first question later. It's important. But the other question-- How  do I setup OAuth?--is answered in the attached document. I wrote this tutorial with the help of my friend and colleague Taylor Sharpe of Taylor Made Services , also here in Dallas. We provide step-by-step instructions on how to get your users authenticating in...

Virtual List Basics

The concept The basic trick behind virtual lists is the wonderful GetValue() function. GetValue() takes two parameters: A list of return-delimited values A number specifying which value in the list to get For example say you have a field in a single record called “List of Values” and it contains the following:    Apple    Boy    Cat    Doorknob    Elephant    Fish When that record is selected, GetValue ( MYTABLE::List of Values ; 4 ) will return “Doorknob”. The brilliant idea is to replace the list of values stored in a field with a list in a global variable . The basic implementation, part one Create a table called VIRTUALLIST. In it, define these two fields: VALUE NUMBER: a number field Value_calc: calc field returning text value, = “GetValue ( $$VALUES; VALUENUMBER )”. Make sure that this value is an unstored calculation. Go to the layout for the VIRTUALLIST table and create s...

Okay, maybe it is partly incompetence

I still think that the problem Healthcare.gov is supposed to manage is such a monster that it would be a daunting challenge for anybody, no matter how competent. That said, it's looking more and more like incompetence may have played a part in the site's epic fail. And I don't just mean normal incompetence on the part of government bureaucrats. How hard was this, really? I myself tried to sign up for an account. With just a little difficulty, I got through several screens where I provided my name, home state, email address, and then, on the last screen, I made up an account name and password. I hit submit or save, and got this: "Unavailable"? They couldn't have told me this before I wasted 10 minutes? Now, when I was expressing my (tentative) sympathy for the programmers yesterday, I was thinking about how hard the hard parts of this problem must be. I mean, this is the system created by a many-thousand page bill whose architect herself said ...