Upgrade FMPA 16 to 17

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Try contacting sales again. Find a partner Become a partner Partner community.
 
 

Filemaker 14 upgrade?

 

Browse all. Shop by Product. Shop by Category. Claris FileMaker Pro 19 Upgrade. Standard Upgrade Edition. Add to Bag. Contact us. Opens in a new window. Product Information. Support for 2-way JavaScript interactions in a web viewer. Prebuilt JavaScript add-ons. Execute Data API script step.

Quick Open. Tech Specs. Internet Access: Internet Access Required. System Requirements. And, this is not FileMaker or Claris bashing, it is a plea for help. Our internal systems are running on stuff that was built, and added to over the past 14 years. We did see some slow down with GTRR in some places, but not everywhere. The main complaints we receive now, are centered around the last gains with Finds, because we had to turn StartupRestoration off.

Other than that, everything is running quite well. I wish I had an answer, I know how frustrating that can be Like themes, or indexes, etc. We’re trying to avoid focussing on this, as it adds a ‘non-standard’ element that diverts from the main issue, hence preferring to concentrate on our Windows LAN based clients’ experiences. The LAN based system we referred to was upgraded a year ago and we’ve worked hard to get around the issues, hence can’t do a representative comparison now.

However, we are currenlty working on another old system that is heavily dependent on conditional formatting, that has ground to a halt since moving to Server 16, albeit still on FMP 15 clients, which we could possibly do a comparison with.

Interestingly, the layout we’re working on to improve performance was setup originally in about 0. We must have spent over hours between us during the last week, building JSON and trying to get all the data stored locally, which is looking optimistic. But those hours are unlikely to not be billable hours and this is something we’re absorbing more and more as we upgrade clients.

It isn’t only our customers suffering from these upgrades. For the record, your internal systems are run on Windows servers and clients? We saw some performance degradation on big old systems when going from 12 to 15 but generally back to on-par performance in The example above is extreme, when it happens what metrics in the stats. I have seen solutions that became faster since FM12 as well as solutions becoming significantly slower. On Windows the reason often was the rendering engine but not always.

My tests comparing FM 12 thru 18 confirm that with every upgrade some things become faster at the cost of some other becoming slower.

I performed over thousand tests but still tested only very small percentage of all possible things that could change between versions. So examining the specific solution in detail seems to be the most efficient way to find out what is the slowdown cause in that specific case. What I can say is that in every optimization we did with my team we were able to succeed without having to downgrade. I would start with isolating different aspects that may affect the performance, such as running finds on blank layouts to eliminate impact of rendering engine, deleting parts of the solution to see if specific part of it has big impact etc.

Also try to replicate the issue on completely different network. You could try to watch the recordings from my FileMaker Konferenz sessions to see if one of the things I mention there triggers your memory about some specific feature or technique used in the solution. You may also hire 24U to help you – disclaimer: I may receive some form of compensation, financial or otherwise, from this recommendation ;-. OK, so it would appear that we all agree that it is necessary to analyse where the problems are if performance issues occur after an upgrade.

To my knowledge, nobody has said that they haven’t experienced any problems upgrading an older legacy system to a later version of FileMaker Server. This seems to be an acceptance of a problem that, to my knowledge, didn’t used to be the case. Yes there were bugs, but I don’t believe that an older system would be rendered unusable just by upgrading to a newer version, particularly when there hasn’t been a file structure change such as from.

This causes us a huge problem. We design systems to empower our customers so that they don’t have to keep returning to us unless they’ve forgotten how to do something or need a new feature.

We are currently responsible for 42 active customers’ systems, some are single files but most are multi-file separated or older legacy databases. If we are forced to upgrade every 2 years without hypothesising about futureware , and this happens on all 42 systems during each upgrade, then we will need to employ more staff and our clients will have to pay more money, making FileMaker an expensive platform to develop on.

This is the antithesis of FileMaker’s value in the market. I’ve just spent Sunday downgrading a FileMaker We upgraded them exactly 1 month ago to the day and their productivity plummeted as per the quotation from the MD in my original post. So far, all indications are that this system is running better today, even using FMPA 18 clients.

It is early days as yet, but if this continues, it is unexpected. So what is going on? Yes, of course, we can spend all our time analysing hundreds of files, but actually, we’re flat out developing new systems and our own productivity is suffering badly as a result. I personally have spent We cannot afford to travel to the US for DevCon to discuss this. Not because we can’t afford it, but we cannot support our clients in Asia due to the timezones.

We would be so grateful to someone from Claris providing some technical background as to why this is happening with systems that have evolved over years and some details that maybe would allow us to target specific areas.

We have a few of our servers upgraded to FMS18 now. And I can say that there ARE changes that made one of our script schedules crawl to a halt. And killed the Scripting Engine. But after lots of analysis I must say I do wonder now how FMS17 did cope wit it in the first place since it was an rogue audit function calculated field that got hammered.

After correcting for this it now is working flawlessly. One thing I reported but since could not reproduce: One of our FM18 Servers did experience a memory leak that vanished after I shut down startup restoration.

But that was the only sever we had this problem and I never dared to torn it on again – it was our in-house production server. It would be so helpful if we had information on these changes between versions. We’re constantly working in the dark and it is just a question of whether it works or not.

 

Download Claris FileMaker updates and resources.One moment, please

 
FileMaker 14 is no longer eligible for “upgrade” pricing. It’s too old. FileMaker 19 is the current version, the only version available for purchase. FileMaker Pro 16 Advanced (Upgrade, Boxed) · Enhanced Data Viewer · Script Debugger · Multiple Table Support · Enable Database Encryption. Get the latest software updates, release notes, and resources for Claris FileMaker. Claris FileMaker Cloud. Claris Connect FileMaker Server