Big announcements from FMI?

Hello everyone,

I have got an email from rcconsulting that could be of interrest to you folks:

Tomorrow (August 6th) at 9AM PDT / (12 noon Eastern) we will be broadcasting live from FileMaker Developer Conference 2019 in Orlando, Florida!

We are told to expect some big announcements. So join us for the latest news.

Watch Live…at Twitch

I will watch, will you ?

1 Like

The “broadcasting” is just going to be Richard talking about what was announced. If it’s not under NDA. It won’t be live broadcasting of the actual presentation.

Sounds like the announcements will be big, though.

I’m a subscriber to Richard Carlton’s tutorials/video courses - I received the mail as well - and will join

hopefully, it’s not just a new episode of farmer John’s ‘better lighting on the workbench’ - thing :upside_down_face:

I don’t believe so. I’ve been told by more than one source, it’s not just hype.

Oh yes, the NDA . . .

What could be the biggest announcement:

  1. Run time will be removed and replaced by something spectacular.
  2. Bugs will be corrected :wink:. Looking at the number of bugs in FMPA and FMS 18, that doesn’t prompt me to try yet.
  3. Yet another licensing system

What are your predictions ?

The only four facts I know.

  • New CEO’s first DevCon
  • Apple acquired a company called Stamplay, and that CEO now works for FileMaker.
  • Brad talked about “possible acquisitions” in his letter.
  • There is no FileMaker branding anywhere at DevCon.

Doesn’t necessarily mean anything, but it’s interesting.

1 Like

Apple acquires Stamplay, but the CEO now works for FileMaker :thinking:.

But wait, Stamplay is Italian . . . let’s hope it’s not another Fi Again Tony.

Draco switching to SQL : YEAH ! :slight_smile:

Not going to happen. Same as an Android version of Go isnt going to happen.

FileMaker IS Apple. They are controlled by and owned by Apple.

I don’t get the reference. But pay attention to what Stamplay is/was.

Which is a major strategic mistake. Tragedic.
But unlike the Android version (which is also a terrible, but less, strategic mistake), there’s no stupid politics involved here.

There are so many things you would lose if they moved to SQL. I’ve had that discussion with the FM engineers and PMs.

Xojo is a good example of what I mean. Devs there that have moved to Xojo, spend a lot of time trying to get it to work like FM. Once watched a video of a dec demoing how easy it is to hook up the data source. The video was 90 mins long. Then the devs went to work on getting that live broadcast and update mechanism of FM. Nothing against Xojo. It has many positives, but the feature set is vastly different. The experience is vastly different.

FIAT means fix it again Tony . . . the cars.

There’s nothing worthwhile we’ll loose going to sql, or postgress.
There’s only 4 functions to rewrite in sql :

  • read / search select
  • delete
  • update
  • insert

The filemaker “advantages” : quick type changes (sql is so fats comapred to draco that changing type will be quicker), multikey, even unstored calc can be emulated easily in SQL, and not to mention that SQL is open source, so they could tweak it if necessary.

Moreover, will gain a ton more : true scalability, true data separation, IT people respect…

I’ve detailed this in the comunity idea thread, I won’t repeat it here.

I don’t trust FMI PMs at all : they were able to create a 40% Slower FMS and write in there doc, how by the way, if you’ve imports just stop the server !
They’re stuck in there faulty mindset.

Last year you came back from devcn overjoyed about the speed gain we’ll get, but we got FMS 18 which realize the exploit of being slower while utilizing more cores.


Frankly, if Stamlay CEO would have been promoted FMI CEO, he’ll probably do this on the spot, but alas we got a salesman instead

1 Like

That oversimplification of what FileMaker does is disrespectful to the development team at FileMaker, and to all developers. Please, show me a demo of your upcoming product…

Which of the PMs have you met? The problem with quoting 40% slower, is that it only applies to single user tests, and it a difference of milliseconds. I’ve done several tests, as have many others, that have shown that under load FMS 18 is significantly faster. So trying to say something bad was done, is a faulty presentation. In tech, everything is about compromise. To get speed in one area, you sacrifice something somewhere else. Given what the’ve done with a v1 rewrite, I’m impressed.

Possibly next week, I’ll have some numbers to show actual affect of multiple users on a low-end mini as a Server. Basic idea, individually the machines finish 1,000 very complex finds in about 11 mins. Running 3 machines doing the same searches, takes 36 mins. When you scale up to 4 cores, you get back to much better numbers. And 18 handles multiple users way better, and it never hits that bottleneck I am seeing with this low-end mini.

Now, let’s get back to the discussion at hand…exciting new coming out of DevCon.

FileMaker is not SQL, so what ??? Those IT people that disregard FileMaker just listen to SQL database vendors, the never put any effort in trying to understand what FileMaker is.

That being said FileMaker and FMI are not perfect. Just read messages on the official Community and look at bugs that are reported about FMPA and FMS 18. I am not a FileMaker opponent, but FMI seems to have dropped V 18. Is it that 1 year between new releases is not enough ? Today I saw that FMI acknowledges a new bug - unfortunately can't recall which one. I couldn't understand how come this went unnoticed during testing.

I also know Xojo. It's a very good tool for OOP development, implementing functionalities to help boost developers productivity, but you can't develop an app as fast as with FileMaker though.

1 Like

Unnoticed. Unreported. Both the wrong words. Fixing a bug is about figuring out what is causing it, changing the code to address it, without breaking other stuff. This is the same stuff we deal with when doing our own development. However, FMI operates at a different scale than we do. There is so much more variety they have to account for. Add on that they are writing code that has to read other much can break so easy. Go build a node.js project with Express. So many moving fragile. Run through that for a bit, and it will give you more respect ( in general, not speaking specifically about you ) for what FileMaker delivers to us.

Many bugs had been reported during testing. At that point, it is about fixing bugs that will cripple files running. Most bugs don't, and we can work around them. Other issues are caused by external technology ( see the issue with Gmail and the Send Mail step as an example ). Hopefully FMI gets a fix for them. But honestly, most of the bugs reported, I've never seen or run into.

Testing is another beast.

I tested V18 much more than any other version since the .fp7 run - and it was phantastic. As Go18 came out, I was surprised because it solved the biggest issue here.
The main reason for that testing was, that I worked a looong day long with V18 without recognizing that - the icon was identical (to 17) on my Mac (I usually have own icons, but due to the fact that I had to upgrade my os’ for 18, I set up a vanilla, new Mac - and did not have the icons on that machine…). After recognizing that I was working with 18 and that was so smooth, I decided to keep on working with 18 - so I tested all ‘my perspectives’…

But: I tested ‘my environment’, just my own habits and needs…

Some of our customers are ISO certified (900x, 27001, etc.) and they must test (one reason that makes it impossible to establish every version of filemaker; one year is way too short, impossible…). The last time, we introduced the new version of fm, user groups were defined to check as much as possible before going live. Some of the groups were late, users couldn’t test as fast as planned.
So, the CEO asked those groups to complete testing until a specific date (it was a short time, just to be ‘on plan’).
All groups finished their testing, sending protocols to dev (I’m the leader of the ‘dev’ there). We had to invoke the new version over a weekend.
Not even printing was working… (but was tested…)

During macOS classic, there was a software called ‘One Click’ by Westcode Software, phenomenal, one could do unbelievable things, interface, scripting, almost whatever…
I was a beta-tester at that time and one westcode-guy was leading all testings, holding us testers straight on a line. We knew every single point and there was an open (for everyone visible) list of issues with their priority.

Filemaker (I’m not a beta-tester for fm anymore) was similar - but not as ‘straight’ - but beta-testing for Westcode took much more time…

At some point, a software company has to publish a ‘v.x01’, knowing that there must be updates. This is normal. What is not ‘that normal’ is the fact that fba testers could not send in any reports (I received a mail telling me that there is no more testing before release)
-> this was changed in the V18 run - we could send in our reports!

What remains the big problem for me is the fact that fmi still has no release notes (for go almost zero, a bit more for desktop version - but far away from ‘full’). Makes it hard to test, to install new versions/patches (I mean, the Japanese-thing doesn’t bother here in any way…)

In short: Today, full-testing became impossible. It has to be a compromise. (nothing new…)

Xojo: I got a professional license (all platform) here. Working on interfaces is much better with filemaker. Overall, filemaker is still the fastest environment that I’m aware of


According to information available on the Internet, Stamplay is a low-code workflow automation tool, similar to Automator but more modern, versatile and cloud-enabled.

When a company wants to make an important announcement to its customer base, it is done through a public statement, preferably a written one. I personally prefer this over the hang-on-the-lips-of-those-who-are-in-the-knowing consumer-world marketing style.