– One moment, please

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Though he was having major problems before that, so trying it didn’t represent anything worse than he already was dealing with. But he suffered from that decision until he got a new machine. Lesson learned and reinforced. Especially on your main development machine, do mess with Beta OSs unless absolutely necessary. I agree. You need a specific machine dedicated to testing any beta OS.

Do not use this for any development work. They cannot release any updates until the final OS is in public release. I am not complaining and I understand the risks of beta software. I am not blaming FileMaker for the problem. I asked if anyone else who was testing Mojave was experiencing the same issue. Any updates or new experiences with Mojave now that release is just a few weeks away? Specifically with FM You should not count on FM16 being supported on Mojave. Likely, but no guaranteed until FM announces compatibility.

Any until the public release is just speculation. That is just the way it is. Apple and FMI do not respond to bug advices only by advertising that Mo NDA to send in as email to:. Dark mode is running well with screen pictures that are made for. FMPA 17 runs only for exec but not for dev.

But shutttt Launch of macOS Why is FileMaker always so late to the game? Other developers are ready for Mojave, yet, the “subsidiary” of Apple is not. This happens with every release, as if the beta has not been out there for months. I don’t get it. What kind of Mac is it? Yes, that’s sad. I also agree that there are many features or bug fixing in the task list but OS compatibility should be on top.

FM want us to use the latest version, Apple want us to use their latest version. But we can not do that. I am not an apologist or fanboy for any particular piece of software or software company, but there’s a lot going on behind the scenes, and a lot for any development team and management to weigh when deciding how to allocate engineering resources. On one end of the spectrum there are the Microsofts and Adobes of the world that have hundreds or thousands of developers.

They likely have entire teams of dozens of people dedicated solely to working on compatibility for individual operating systems. On the other end of the spectrum, there are the little boutique apps and app developers who don’t have to support multiple OS-es, multiple OS versions, etc It’s a lot easier to keep up to date when your only platform is iOS. When a single person Clay can sit on the stage at a DevCon session and answer deep, thoughtful questions about the inner workings of FM Pro, how it communicates with server, how it parses SQL-style queries, etc Additionally, during OS beta cycles, the feature set is a moving target.

There is solid evidence that Apple drops features, APIs, etc I firmly believe that FM, and any software company, is doing all it can to make the best decisions on how to allocate engineering resources.

They gain nothing by upsetting their customers, and gain everything by keeping as many of their customers as happy as possible. So anyway I, myself, will likely try it out this coming weekend when I have time to roll it back if it blows up on me, and not lose billable hours in the process. I will reply with my experience as soon as I can assess. I’ve been listening to a number of podcasts, including the MacAdmins podcast. They have talked often about the number of very significant changes happening throughout the beta process with We have to ask ourselves, what is more important, zero-day support?

Or continued development of new features. Whether we like it or not, the speed of development isn’t going to change. FileMaker has the resources they have.

And they put a VERY significant percentage of their revenue directly back into engineering. Keep in mind that ‘Mojave’ does not necessarily mean “voluntary update from an impatient existing user”; it could perfectly be a new FileMaker user who just own a brand new Mac; or an existing FileMaker user who had to buy a new Mac because the existing was dead. A compatibility update is planned. We are trying to hold off buying any new machines until after October, in case there is a hardware update.

Hey Josh, please be serious : this link was posted many times today, especially in this thread. What do you mean? The first 2 paragraphs talk about the planned update and timing. I too was tricked into reading it 4 times. Which is why it’s both funny and serious!! Honestly if your going to buy a new computer in the next month it is more probable that its not going to have Mojave preinstalled. That being said I would have expected an update within weeks not months.

Considering the mostly cosmetic issues. I do enjoy everyones speculation why it takes so long. I would bet the contrary : Apple is very experimented in this game. My last comment, just a citation afterward you will have the last word, i promise :. I guess that would be true if you buy directly from Apple.

They are notoriously good at managing their supply chain. They worked great until the drivers were broken with the The problem is that they are still broken. But, guess what? They work perfectly in Mojave. I can tell you, being able to work on 4 screens at once is a huge benefit. Especially for someone who has the short term memory I have Namely, that I don’t have any short term memory.

How much fun will that be if we have to build FileMaker Go solutions in Windows? Just reading back, maybe I missed it. Can you articulate exactly what problems you are facing? I only know of a few, and those ones aren’t deal breakers. I am genuinely curious. I’d be up for reproducing anything that is not known, and helping to supply FileMaker with more info about what is broken.

MacOS will always be supported in FileMaker. There’s nothing in the update information that says otherwise, and speculating as such is not useful to anyone, nor is it allowed on here, in FileMaker’s community posts.

There are many folks at FileMaker watching this thread. Most of this thread is useful to them. The known issues with Dark Mode and things not being visible are pretty substantial for me. There are only 2 developers in my company, we use Macs, and are 2 of the 3 people using Macs at the company now. There used to be more but were transitioned because of another apps issues. Other than Dark mode which I don’t consider an issue , I’ve never seen any ‘things not being visible”.

When I first upgrade the OS, I didn’t see the operator buttons in the dialog, but I never use those, and there’s an easy way to reset the GUI in one step. At Geist Interactive, we upgraded day one and haven’t had any issues. Frustrating and I see no outreach from FM to compensate its customers for the failure. Clearly FM has early and minimally beta access to macOS versions for development.

Have to inform you I deleted my post that you answered, since it was noted “under moderation”. Never saw that in my life I changed my comment. None of our servers are on mac machines. I do not think of issues of My fault.

Not FMS We use windows machines for server. What about Mac only shops? What are you seeing them do? Because I didn’t “Delete” it or set it for Moderation. For what? Don’t upgrade your server to Mojave. That’s not hard to comply with. This conversation is heading back into the ridiculous. So when you are stopping the Web publishing engine, it may crash. Restart it. I agree, this is a rough on IF you are using the Web server for something.

This may be a big deal for you. Again, though, why is your server on Mojave? It will run on Sierra or High Sierra. There is only one scenario I can think of that forces you to install FMS17 on Mojave with no other choice. These are deal breakers for moving to FileMaker staff are watching this thread, and all other threads. It is a fact. Had a conversation with at least 4 different FileMaker, Inc. A fix is coming.

It will come when they have sufficiently fixed the problem. It’s not really fair for us to try and tell them how long it should take. No different than someone that is not a developer to tell us how long it should take to build a feature or fix a bug for them. They wait until FMS is ready for Mojave.

I don’t see that as unreasonable. FMS 17 works very well on High Sierra, right? It’s not like we’re suddenly without server. New Mac minis all Macs only ships with We are indeed using Web server for several integrations. It lasts for me. That’s weird it doesn’t last for you. In your case, I see, the new machines are greatly needed. I get the problem. For other macOS-only shops, it might not be such a great need.

Have you considered a hosting service until the patch is released? If you must stick to Mac hardware then get a new powerful piece of hardware and put VMware on it, run Windows or a supported macOS virtualized. Seems that this would work without too much hassle until a fix is in.

For running FMS I don’t really see the lack of Mojave support as a big deal-breaker at this point since the number of deployments you’d need to cate for is going to be manageable. Try what maxlatitude pointed out. External drive, with High Sierra as boot drive. That will give you the new mini with High Sierra until a patch can be released.

And a fairly inexpensive stopgap. Since i never use them, I totally forgot they’re missing. It’s fine. I barely even have the function list open either. All type-ahead for me.

To wimdecorte Thanks you. Appreciate the idea. It’s somewhat part of ‘create Your own app’. No problems with FMPA 17 on Mojave in general, but still using the 3 day old Mac Mini as a flower pot stand until we decide what to do. Or get yourself a text expander. See my options. When you are done with the external drive, use it as a back up drive. Dumb question alert If so, anyone care to share? Mainly would be nice to know how to type: return character, not equal, greaterthaneqal, and lessthanequal This info should be out there for everyone.

And I should have mentioned it in a previous post. Well, the fact that FM automatically puts a space before and after the operators is kinda nice though. No problems with the page 4 instructions. We’ve a metal recycling system upgrade due for installation this month and would have held off a few weeks if the November Mojave update was released on schedule.

With it having slid to sometime in December, we’ll probably go for a stop gap solution, hence using the external SSD rather than having to scrub the internal SSD a few weeks hopefully after we go live.

I still find it interesting, as a business owner who is focussed on issues affecting our company more than the software, that FileMaker 17 is compatible on Windows back to an operating system that was originally released 9-years ago and only compatible with a Mac operating system released 2-years ago. Technology advances vs return on investment, cost of ownership, etc. Here, customers do have a ‘plan B’ switch to Windows. I just think there will be a move to cautious software evolution in the future, rather than an annual revolution that is, without doubt, disrupting our businesses.

My other comments regarding how Microsoft are drip feeding new features in Office point to the way the industry needs to go. The days of trying to court users to buying cellophane wrapped boxes with a new version number has long gone, I still think software is going to look pretty stupid celebrating their MySoftware v21, or having a mid-life crisis between MySoftware v30 and MySoftware v Instructions can be found on YouTube.

Well, the obvious and only thing that Apple mandates is that they don’t do an Android Version by all means. Probably still the dogma to go ‘Thermonuclear’ over Android.

I had the first customer calling me about support of the new MacMini which only ships with Mojave and the fact that he can’t get FMS I haven’t received mine yet. Adjusting the external boot option is for the High Sierra installer on a USB stick, etc, or to install and boot High Sierra from an external drive. Feel free to PM if you need assistance. For reference, I got my Mac Mini a couple of days ago and tried to get it booting into High Sierra.

It did not work. Despite enabling external boot and reducing the secure boot level from Full to Medium, I was unable to boot from either a known good High Sierra installer I was able to boot from an external disk with Mojave cloned from the Mac Mini’s system to prove that external boot worked. The closest I got with High Sierra ended up in boot recovery saying the startup disk needed to have a special update installed, but none was available.

My Mac Mini has the 3. I don’t have access to any Mac Minis with a Core i3 or Core i5 so I haven’t been able to redo my test on those variants. This is false. Server 17 works fine on APFS. There is no documentation that states APFS is an issue. No issues other than those identified in the support articles regarding PHP etc. I can only imagine the stress these yearly upgrades have on the development teams.

It’s hard enough shipping software as it is without artificially induced deadlines that appear more aligned with marketing rather than technical need.

Reply to this message by replying to this email, or go to the message on FileMaker Community. Start a new discussion in Discussions by email or at FileMaker Community. Following Re: Mojave Compatibility in these streams: Inbox.

Some issues were identified during the Mojave beta phase but those were related to very specific third party hardware configurations. My understanding is that these issues don’t even exist anymore. Mark, I worked for a Mac support company for 15 years from the early 90s.

I remember a very large, long project involving Xserves and rolling out Open Directory across a private school. Half way through the project, having purchased and gradually rolled out the initial Xserves, Apple released an OS update when it wasn’t possible to guess when the next one would be released and from that day all new Xserves shipped with the new OS that was totally incompatible with the previous one as far as Open Directory was concerned. The project had been planned meticulously and was going very well until then and the proverbial hit the fan.

The problem now is that this is happening every year and does undermine the Mac in business, despite all the other advantages it provides. Thanks for your contribution. Mac Mini: I called Apple support yesterday because all my data is on a thunderbolt raid and I need that data on the new Mini I’m about to order one of the 6 core ones , what adaptor, etc. Personally I am not a big fan of those comparison thingies and almost always use.

Easier to read for me and no special characters involved. Do WE really know what it means? What should that mean for all products for any division of ‘parent company’? Apple divisions for MAC certainly never communicated with the Apple][ folks, for example. This is particularly problematic if you work in a large organization—as I used to, and now continue to consult for—where FMP is a “non-standard” application that the in-house IT folks are looking for any excuse to abandon.

IMO, the desire for abandonment is primarily because they’re too dug-in, lazy, busy, or some combination of all three, to learn how FMP could improve their lives if they let it; however, that’s irrelevant when FMI is handing them, “on a platter,” the very ammunition they need. We have a pretty deep and wide technology stack.

If FileMaker is the only thing keeping someone from upgrading the OS, their technology stack likely isn’t that deep, and it’s very possible they don’t have an IT department of any kind. For FileMaker Pro Advanced, the issues are very minor for most people. For FileMaker Server, there is only one issue that would cause any concern.

And that only applies if you are using the Web Publishing Engine. Even for this, there are fairly easy solutions to handle it. No different than you get with any other piece of software. I agree with you that some IT departments view FileMaker with little regard. That is just ignorance.

They can be educated. This minor thing with Mojave, is more likely to have Windows IT departments pushing to not support Apple FileMaker aside. And we are only weeks from a patch anyway. In my experience, most IT departments are not ready to start using Mojave yet. One case as an exception where they buy a new machine. As the strategy is evolving and is demonstrated by the developments to the product already, the roadmap and especially the changes being undertaken on the server side then FileMaker appear to be pivoting to a different market segment.

I recall having read that High Siera will still get security updates for many months, so security is not an issue then. Maybe putting more efforts and funds into technical stuff instead of marketing would be helpful for the maybe forgotten developers.

Which is why I personally am still using Sierra. I am hoping we can install Sierra should we purchase new Macs! Thankfully for my clients, they are for the most part using Windows. Sorry, we’ll have to agree to disagree on that one maxlatitude, wait for at least the first v. Running a large or small network on a non proven OS is not for us.

It’s obvious you have not been to DevCon the past few years. They actually talked about this. They put a significant percentage of sales directly back into engineering. Much, much higher than I would have ever thought. It is important to understand the company, their vision, and their strategy before making broad-sweeping, very inflammatory statements. Talk to the engineers, and the Product Managers. You will not find a more passionate group of people about the product.

They have reasons for why things are done the way they are, and why they don’t do certain things. They have a the roadmap, which we see and they talk about openly. They also have a long term plan that will ensure FileMaker is relevant long into the future. Those changes, which are more important than feature requests from us, we will never “see”. But they have to dedicate time to them. If not, the product can’t survive.

And we are talking FileMaker Server here. That point needs to be clear. I just downloaded the trial version of FMP 17 and it is working in Mohave.

I definitely agree there. If it’s not necessary to upgrade at the time of launch for some reason, it is wise to hold off a while. And with mission-critical setups, not a good idea to upgrade for a significant timeframe. My point is that software developers, in general, should aim to match the OS release dates with compatibility updates. Interesting adoption chart on that page. I want to thank everyone for jumping in and discussing this so passionately.

I think we all have learned a few things for sure. I think in the end this comes down to maybe pulling the scabs off some old wounds with regards to being a Mac user. I’ve been using a Mac for about 16 years now.

When I got my first Mac back in , it always felt a bit frustrating when the platform was “Neglected. The fact is there are 3 distinct use cases here we are discussing. As a developer I have a copy of server 17 running on my machine right now, right next to FMPA 16 and Then I have a VM running 16 and 17 as well.

I’m tempted to just pull the bandaid off and live with it for a month. But, the bigger issue is I just don’t know that the frustrations are worth it. If we were looking at a week or two that could be one thing. However, we aren’t, they just bumped it to December timeframe, and we have Thanksgiving and Christmas holidays coming in the next 6 weeks and then New Years. That’s 2 or 3 weeks out of the 6 possible before the end of the year.

I know how software development goes, you all know how it goes, I won’t at all be surprised if we don’t see the update sometime Mid to Late January at this point. I see your point. I guess it depends if a bunch of developers are employed fighting OS related issues, or you’ve one or two computers put aside for this purpose, and the remainder retain the proven OS.

A word I repeat frequently on posts I contribute to is ‘productivity’, which doesn’t seem to appear much otherwise. As software developers, this can be the difference between success and failure within business along with the associated cash flow.

I agree, we need to keep abreast of technical progress, but not at the cost of getting work finished. Just as a side note, searching on unindexed fields can sometimes be replaced by sorting on these fields. You’ll get a stoppable sort dialog, with a real progress bar. And by looking at the sorted data you can isolate what you were looking for. Filemaker is blazingly fast at looping on records. I agree that FileMaker could be quicker to release a compatible version. I know that when beta iOS is out, I always test my apps to ensure they are going to work and if needed have a fix ready on or soon after release date.

Maybe have a Transition Team that does just this Interesting thread to read. Instead their statement suggests it is compatible with a few known issues. I guess that is true from a legal perspective, but saying “not fully compatible” would have been more clear and more honest. It at least could have cautioned users from upgrading to Mojave. Though would not have helped anyone who has bought new equipment.

I don’t know what “as quickly as possible” looks like. But I’m doubting it is months and months after Mojave went into public beta, and mucho months since it went into private beta. I DO grasp how it takes up engineering time to try and revise an app to a OS that is still in beta. On some level it can seem realistic to wait till the OS is out of beta before addressing the concerns. But I’m just not sure how realistic that is in this very competitive time in which we live.

I recall there was an issue where operators did not show. The work around was to reset dialog boxes and positions from Preferences. I’m not using FM17 although I have it installed , so there could be other issues I am not aware of. They do this already.

The process restarts when the OS is launched. Because, well, things change. They already have part of engineering time is spent on this.

With Mojave, in particular, significant changes happened. They had almost a dozen beta releases in less than 5 months. So far, the thread has only mentioned 2 things. We really want to make sure that any issues are in the heads of the engineers. Since they are neck-deep in testing and finishing the patch.

Do you think they don’t want this? Testing and fixing FileMaker from their end is x more complex than us testing our files for any issues.

They have to plan for all the crazy and varied approaches of ALL of us. That is not trivial. I refer back to my earlier comment, the staff at FileMaker, Inc.

When we receive the patch, you will have your answer. That will be as quick as was possible. I really appreciate your contribution to this thread. But I think that one of the things that might be missing here is all the different ways in which people work. YOU might not be having “Significant” issues with Mojave. That still doesn’t mean other’s aren’t. Additionally, by your own admission, FMI doesn’t start “Testing” things until they get it into our hands.

What happens when Mojave is installed on a wide range of machines with developers running Mojave and more issues arise? I really do appreciate your perspective and knowledge, however, I just feel as if your experience might not be the same experience as everyone else. Josh, you have a reputation so I won’t engage. Your rant uses words like “not trivial” and “x more complex” when NO ONE is suggesting it isn’t complex. To be clear, I’m only interested in defining the issues you are running into.

If there are issues beyond the known issues listed in the kb article, it’s important for all of us to identify them. I believe the time frame for these fixes needs to be adjusted.

After all Filemaker is Apple. Any ideas? Specific instructions will be much appreciated. Right click the file and open it with filemaker Then if you want you can export your data from the trial version or buy the latest filemaker to continue using it. But you got me thinking of a different approach below and it worked! Thank you!! Success all around! Thank you. Create apps in the cloud. Run apps on iPad and iPhone. Runs apps in a web browser. Share apps with a team. Latest enterprise-grade security with end-to-end encryption.

Single sign-on, OAuth, and multi-factor authentication. Architected for privacy by default. FileMaker in action. Try Try FileMaker Pro free for 45 days.

Try now. Contact us Talk to a sales rep about a custom plan. Call us.

 
 

 

Filemaker crashing since Mojave update –

 

However, some people may be curious to know if there are issues working with Mojave before and after it’s official release. The import source is an Excel file approximately 28 Filemaker pro 14 advanced mojave free. I was having the same import problem with High Sierra but the issue in file,aker mode is new. Be aware that Apple Inc. Party HD. Is that block just for the beta? Or is it a core OS change? Apple Inc has closed my Bug Report and advised to send new report when this issue still appears with GM.

There’s a chance with a work around by installing Mojave, followed by last TimeMachine Bup on a fresh Mac, make TimeMachine Bup and use this to perform a recovering to your 3. Party SSD. A helpful, and professional response, right up until that last line. It’s just not acceptable. I am sure FMI is very aware of any issues with the macOS beta and are working to make sure everything will be ok.

Wow, that sounds only slightly better than FMI: “Yeah, we won’t do anything about fixing those bugs that make your experience with the prerelease software totally useless, until the final release version. IOW: “The next beta will be the one we release to filemaker pro 14 advanced mojave free general public. My Maybe That would suck but not surprising. Not sure what issue you have but it could be just a bug with your particular hardware type.

MBP 13″ Retina 2. Apple requested a full SysDiagnosis which I sent in. They checked and confirmed that Mojave NOT installing on this drive is not a bug. We recommend waiting till the full release of the OS so that we would be able to start our in-house testing with our products. Please avoid thge use of Приведенная ссылка on OWC products as of this time.

In the latest build of Mojave beta 3 Filemaker doesn’t crash anymore in button bars and buttons. That’s great news. Is the build moojave for beta 3 18Ag? I’m curious about how FileMaker will handle dark mode. Will it be detectable? It would be nice to have an alternate theme for dark mode. Only time will tell. Imma gonna guess that that one is pretty far down the list of advancced, no matter how far up the wow-things-it’d-be-cool-to-have list.

Handling a layout’s design will filwmaker be our responsibility as developers. If we do get a boolean to check for dark mode, I could see maybe using conditional formatting to alter an object’s style. After updating to the latest version of Mojave Every подробнее на этой странице I interact with the Script Editor in any way I get a long spinning beachball.

Clicking anywhere or typing a single filemaker pro 14 advanced mojave free triggers the beachball. My boss made the mistake of upgrading to the Sierra beta when it was out. Though he was having major problems before that, so trying filemaker pro 14 advanced mojave free didn’t represent anything worse than he already was dealing with. But he suffered from that decision until filemaker pro 14 advanced mojave free got a new machine. Lesson learned and reinforced. Especially on your main development machine, do mess with Beta OSs unless absolutely necessary.

I agree. You need a specific machine dedicated to testing any beta OS. Do not use this for any development work. They filemamer release any updates until the final OS is in public release.

I am not complaining and I understand the risks of beta software. I am not blaming FileMaker for the problem. I asked if anyone else who was testing Mojave was experiencing the same issue. Any updates or new experiences with Mojave /36501.txt that release is just a few weeks away? Specifically with FM You should not count on FM16 being supported on Mojave.

Likely, but no guaranteed until FM announces compatibility. Any until the public release is just speculation. That cree filemaker pro 14 advanced mojave free the way it is. Apple and FMI do not respond to bug advices only by advertising that Mo NDA to send in as email to:.

Dark mode is running well with screen pictures that are made for. FMPA 17 fred only for exec but not for dev. But shutttt Launch filrmaker macOS Why is FileMaker always so late to the game? Other developers are ready for Mojave, yet, the “subsidiary” of Apple is not. This happens with every release, as if the beta has not been out there for months.

Читать статью don’t get it. What kind of Mac is it? Yes, that’s sad. I also agree that there are many features or bug fixing aevanced the task list but OS compatibility should be on top.

FM want us to use the latest version, Apple want us to use their latest version. But we can not do that. I am not an apologist or fanboy for any particular piece of software or software company, but there’s a lot going /9558.txt behind the scenes, and a lot for any development team and management to weigh when deciding how to allocate engineering resources.

On one end of the spectrum fgee are the Microsofts and Adobes of the world that have hundreds or thousands of developers.

They likely have entire teams of dozens of people dedicated solely to working on compatibility for individual operating systems. On the other end of the spectrum, there are the little boutique apps and продолжить developers who don’t have to support multiple OS-es, multiple OS versions, etc It’s a lot easier to keep up to date when your only platform is iOS.

When a single person Clay can sit on the stage at a DevCon session and answer deep, thoughtful midas gen 2015 crack free about the inner workings of FM Pro, filemaker pro 14 advanced mojave free it communicates with server, how it parses SQL-style queries, etc Additionally, during OS beta cycles, the feature set is a moving target.

There is solid evidence that Apple drops features, APIs, etc I firmly believe that Mojage, and any software company, is doing all it can to make the best decisions on how to allocate engineering resources. They gain nothing by upsetting their customers, and gain everything by keeping as many читать their customers as happy as possible.

So anyway I, myself, will likely try it out this coming weekend when I have time to roll it back if it blows up on me, and not lose billable hours in the process. I will reply with my experience as soon as I can assess. I’ve been listening to a number of podcasts, including the MacAdmins podcast. They have talked often about the number of very significant changes happening throughout the beta process with We have to ask ourselves, what is more important, zero-day support? Or continued development of new features.

Whether we like it or not, the speed of development isn’t going to change. FileMaker has the resources they have.

And they put a VERY significant percentage of their revenue directly back into engineering. Keep in mind that ‘Mojave’ does not necessarily mean “voluntary update from an impatient existing user”; it could perfectly be a new FileMaker proo who just own a brand new Mac; or an filemaker pro 14 advanced mojave free FileMaker user who had to buy 144 new Mac because the existing was dead.

A compatibility update is planned. We are trying to hold off buying any new machines until after October, in filemaker pro 14 advanced mojave free there is a hardware update.

Hey Josh, please be serious : this link was posted many times today, especially in this thread. What do you mean? The first 2 paragraphs talk about the planned update and timing. I too was tricked into reading it 4 times. Which is why it’s both funny and serious!! Honestly if your going to buy a new computer in the next month it is more probable that its not going to have Mojave preinstalled.

 
 

FileMaker Pro operating system requirements – all versions –

 
 

Is that cool that filemaker is always late, no it’s not cool. Would it be better if it wasn’t, of course! So, Filemaker should be ready the day of the realease, or a week after max. It’s one thing to brag about Workforce innovation platfform, and then fall appart just when the user wants to innovate with the latest upgrade.

That’s a total marketing disaster. Moreover, for us Filemaker devs, it’s just complicatig our work for nothing. Because FMI is not ready, then we’ll have to justify, and advocate, escuse, convince. Lots of wasted time, just because FMI is not ready. That’s it, tahts’ perception. And the inly thing that count is pereception.

User wants to upgrade,. And that’s the perception we need to break. You are not in control of the release cycles of Windows, Apple or FM. But you are in control of what your customers use. If not, then again, like I said before, it’s a missed opportunity to tell them what is important. If they don’t listen to you about this, then you can’t really give them the value that they are after.

And the reality these days is that the client may have to forgo “dark mode” for sake of stability. This tells me your technology stack is pretty small then. And that’s fine. This is still an expression of your own experience, and not the experience of all users. FileMaker has never held us back from upgrading. At least not alone.

There are so many other things that get in the way before we even can think about upgrading FileMaker. At my place, Filemaker is the only software with such issues, that’s it. It’s also important to remember FileMaker doesn’t have a team of engineers. Having zero-day compatibility is rare, and those companies that do it are significantly larger.

Why should I not upgrade say the user? So Filemaker is the culprit. If you are not in control of your environment then you have no control whatsoever. It does not matter whether your chosen platform is FM,. NET, Java, or anything else. If you think otherwise then you are just deluding yourself. The fact that you are being bitten by the combination of macOS and FM is purely coincidental.

It would and will happen to you with other platforms too. You develop to a certain business spec and a given framework. That is all you can promise. If the client goes beyond that then it is outside of your envelope. If you think FMI is going to solve that for you: nope. Not going to happen. That’s yours to solve. The ensuing discussion, yes, has been helpful. This post started off in a rant, but has actually evolved sort of into less ranty and more discussion.

Not sure I’ve ever seen a post evolve. Everyone, this is a healthy discussion about important topics – release schedules for FileMaker platform software in relation to OS releases, and compatibility with non GA versions of FileMaker. In my opinion, the current software release life cycle for the FileMaker platform is flawed, coupled with the diverse licensing strategies – not very Apple like, but FileMaker is it’s own thing. This opinion is shared by many in the community, and I understand why others are not so up for the discussion – what can we do?

The important thing is having these discussions, in dedicated topics, to discuss from time to time. There’s no need to lay blame any anyone’s feet – each company and development team have their own strategies and software life cycles. Personally, if I were in charge, FileMaker would be an annual subscription platform, on a per user, perhaps per server basis. Volume discounts. Reasonably priced, but certainly maximizing profit potential. Pricing is transparent and available on a pricing page, and no need to call anyone.

Continuous release cycle. The most up-to-date version always available to subscribers. Compatibility releases with each OS release. I’d really like to know how much coders there is at filemaker? FMI is hiring like crazy. They have software engineering teams in CA, TX, Given the tightening job market for experienced developers, I also wonder how many seats are hot, and how many are ready to fill.

I’m not sure, and I’m not sure Adobe tells us how many engineers they have. Do you think that’s a number any company would want to give out? What makes you state this as any kind of qualifier? What if they had one super-engineer doing all the work of engineers at another company? How is this going to sway any argument in the thread so far? Meh, workforce productivity ratios, but we’re missing a few variables.

I’m not asking FileMaker to solve anything for me, I just ask them not to create problems themselves by not being able to update their software in a timely manner like tons of other companies do, especially if they’re apple owned. I’m just saying that this Mojave compabitlity issues are just a total PR disaster, demolishing marketing and advocating efforts, and that’s it shouting themselves in the foot while other companies, that aren’t apple owned have no such issue.

Your sound deployment advises have nothing to do with the issue, the issue is that Filemaker is super late in the Mojave compatibility stuff, that it harms the platform perception a lot, make us waste time to explain user, but also make us responsible admin postponed upgrades that users want or need new macs.

That’s just a waste of time and efforts, like the very existence of that thread which would have never existed just if FMI could release that dam upgrade like tons of other companies untied to apple furthermore , do.

So the point of that thread is to tell FMI, that this delayed upgrade stuff is hurting the platform a lot, that it can’t be possibly seen in a good way by regular users, and that as an apple company it’s even more important. When you want to do marketing, you try to avoid bad stuff. So I’m telling FMI : don’t overlook this, don’t shy way, it’s important.

Did I? I did not brought this topic. Since somebody else talked about it, I was just asking out of curiosity. Because I’m curious about it. The qualifier may have been in the perceived intent of the post in the sequence of the thread. I was trying to interpret why the number of FMi engineer would have any bearing on the topic at hand,. Since neither you nor I are native English speakers we can probably leave it at that. I have hope for it. Cool, knowledgeable people are here that can steer it the right way.

Does anyone find it peculiar, the way I do, that I get all kinds of email notices from FileMaker, including telling me things I don’t need to know e. Instead, I get the news from colleagues and threads like this one.. On September 24, a blog post here was put out about FileMaker and Mojave. While Filemaker’s major updates 14, 15, 16 and 17 added a lot of UI functionality and were very welcome for improving the limited way we had to present data, I can not really say I’ve noticed the same for annual OS X releases.

What concerns me more is the now annual version upgrades for both Filemaker and the OS X and the never ending dot version updates which also have to should be tested before going into production.

More headaches I don’t need. Nag dialogues for updates and new releases don’t help and hardly reinforce the cautious approach users should take before upgrading. I guess what I’m really pissed at, is lack of stability and bugs in early version releases are considered acceptable in this day and age, marketing and releasing new versions seem more important than bullet proofing what we already have.

I got stung with the hike in maintenance agreement costs this year, I locked in for a further 3 years. I’ll happily take the updates to come over that time as OS X transitions to full 64bit, but when this current maintenance agreement expires I’ll take a cold hard look at the Filemaker platform, FMI have massively increased their “spoils” from the gravy train but are now giving precious little back for the increased cost.

Screenshot taken today. No information that there will be an update including Mojave compatility. I still struggle with this. Maybe, it’s a question of where to set the focus.

Maybe there are more important things WIP with all the need of related tools. If the daughter doesn’t have the necessary information – who else? I tried to vote it up but cannot access to your idea, get a “generic” error. Strange, seems to be broken. A three months period for achieving compatibility with a new OS version is fair game.

This should be the policy. If there is, for a particular version, need for additional time because of unforeseen difficulties, proactive communication helps a lot. FMI should make sure that all resellers beginning with Apple proactively communicate existing compatibility limitations i. There could also be a ‘check system compatibility’ button right on the webshop landing page that gives direct access to compatibility information, or a technical FAQ like the one for licensing.

Both FMI and Apple marketing is all about the ease if of use. While I agree somewhat with your comment I think that the product is maturing at a faster rate then we have seen for some time.

At last focus is being given to the issues that have prevented FileMaker use in larger scale projects – Clay had a slide that shows the underlying work that is being undertaken to remove the Java stack and replace with Node. JS for the server technology. This is a huge engineering project that will deliver many improvements in the coming years. They have limited resources, have a seemingly somewhat hands off approach from Apple and a very active marketing team.

It must be a struggle internally if you are in the engineering teams. I can second this. V 17 is a net improvement when coming from v 16 and we have to salute FMI for this notable exception: the left-outs in the server GUI. If marketing touts ease of use ahead of anything else, closing the compatibility gap with a new OS version within 3 months should be part of the planning. If not, a disconnect between marketing and engineering becomes obvious. I do not think that a three months period is cool.

There might be reasons for this – but it’s not cool because many people are waiting for new Mac’s I would also expect that FileMaker Go 17 is allready ready for the new 11″ iOS devices – they are not but this is a minor problem, it’s just the screen size that differs a bit. Not only the missing [operators]. I have a very strange behavior in custom fonction windows too: Every click leaves a blue mark. Don’t upgrade??? Which is somewhat of a shame.

Same with my 13″ MBAir. Louis, be happy, you can read the text. From my side, I got the most part of time blank screen. This is not my case, nor is FMP As far as plugins are concerned, this is not possible in all cases. So I’m forced to deliver a runtime solution to it but no way to plot a graph in the Runtime version of FileMaker unless you add a PlugIn.

Same for another more vertical application that requires the use of RSA coded headings, this is not a fantasy, it is the law for this application to be approved by the tax authorities.

It is still surprising that five and a half months after Mojave’s first rush, an Apple branch is not able to deliver a version that works properly on Mojave.

Personally, I tried the first beta version of Maojave from June 12th. I mentioned this fact on a thread, the only reaction FileMaker was a threat on the pretext that I exceeded the guidelines of Apple DNA about beta softwares. Again, I got the impression as I right now that FileMaker does not care about the advice of developers and users. Next year we will have the same state, in May a new version 18 of FileMaker that will be not compatible with the next version of macOS.

I’m testing another environment like 4D to do the same thing as FileMaker. This is a huge investment that I made by learning how to use and then develop on FileMaker and I am very disappointed by the lack of engagement of the FMI with members of its community. We got quite some customers running FM For some of them, going to 17 is planned, for some of them that’s not possible for several reason. I also got virtual machines, besides of the startup time really fine, fast and smooth enough for FileMaker.

But not enough space on the ‘Air’ or on the touchbar MacBook. Mojave VM takes nearly a gig’s Excellent machine with crisp display. Definitely true that budgets and resource allocation play a significant role in this. Budgets and resource allocation reflect priorities and when I see idiotic videos that must cost a lot of money I can’t help but reach the conclusion that marketing is winning those turf battles.

It is completely illegal, and rightly so, for Apple to give any of its subsidiaries a competitive advantage! It is not true to say that FileMaker is the only application with compatibility issues. Some never will! This is a major Os release, there are bound to be some wrinkles!

The blog post certainly does not explicitly say “bury this in the community where only the most devoted users will see it” but it seems to be evident between the lines.

Also, it is worth noting that since September 24 the blog post has had only 25 comments where as this one began 2 days ago and already has triple that number. Thanks to your reminder about it, I now recall reading it and advising some of my clients to hold off until further notice, and the leaders of my local user group mentioned that the consequences are more serious for Server than for Pro.

As to the number of engineers, perhaps you’re right that engineers is too much to expect. If that’s true, I’d like to start the bidding at The quality of some of the responses here shouldn’t be overlooked. People complain about 17 being unusable in Mojave, which is not true. Lots of noise that doesn’t contribute to the discussion. As far as the number of employees, I think guessing veers into the “speculating” category that we’re asked to refrain from in the forums. I am good friends with many people at FMI and I don’t know how many.

I don’t worry. I know they’re working hard to make the platform perfect for us. We are in a cycle that will eventually be broken, because it always happens in IT, particularly as business and large organisations will not accept continous change, there will be a backlash and the likes of IBM and SalesForce, who have publicly been announcing their adoption of Macs, will kick back and demand stability and continuity.

Apple will need to decide if it is only interested in consumers or leave business to Microsoft and Google, Linux or some new upstart as they did with servers. Microsoft appear to have got it, with weekly announcements of new features gradually released within Office No fanfare, no version change, no backwards compatibility issues, just a quiet announcement of something new. AVLA gives FileMaker the same opportunity if they choose to take it, rather than an annual cycle of bug fixes and no new functionality.

Currently, we have about 6-months opportunity to use the current versions of Mac OS X and FileMaker before the cycle starts again. We have no responsibility or influence over these, many are in non-English languages. Even solutions that rely on browsers are not immune from compatibility issues, Safari v12 removed NPAPI, as did Chrome before, that has broken many things until they get fixed.

Yup, higher complexity for us, not our users and cost, but none of the day-to-day issues being raised above. We do feel the pain expressed here, but eventually the industry will wake up and smell the roses. Citing a famous sci-fi movie android: this is madness! We came to the point were botched OS updates turn devices into bricks.

So based on the current schedule Since a patch is expected this month. You are of course expecting the patch to fix the issues and not introduce new issues as has happened in the past disappearing scripts. Personally I’ve been running Server 17 on Mojave without too many issues except for remote user counts not being released. I haven’t done any major development work in 6 months as I’m waiting for things to settle down before I incorporate new UI schemas.

I enjoy developing and exploring now ways to utilise FM for our Business processes. But I will not complain to much after 6 years of service without a breakdown. I can’t care less than I do about not having metal on a machine which will run Filemaker Server for its whole life, without a screen attached to it.

This is not exactly what I call “without problems”, but it does allow clients having problems with their old macmini servers who HAVE to buy new hardware to get the latest MacMini , install High Sierra and run FMS 15 on it. Our clients do not care about having the latest OS from Apple. What they care about is to be able to replace a dying – worn out – old – machine with a new one and have exactly the same stuff they had working the same way they are used to. Because for them Apple is a hardware company and Filemaker a software company.

And this simple truth goes often forgotten. You’re welcome. Only a couple extra steps, since recovery mode is required for reinstallation anyhow. If there is any solace, WebDirect is compatible with Mojave If there’s one thing that OS upgrades generally don’t break, that is functionality of the web.

Has the time has come to build for webdirect and ios only? That might be the road happiness. As mentioned elsewhere, we have a couple few? We’ve now disabled the Mac OS upgrade notifications.

FMP 15 is installed on those particular Macs and seems to be working fine, so they will stay there for now. The next version will be 17 unless our test group meets problems, then it’ll be This is business, not “arts and crafts” no offense intended to artists and these non-synchronized version cycles are costly. As developers, we need to run older versions – as long as there are customers who are running those.. We do have VM’s, but it’s easier to work directly on the os of the machine, especially under macOS Windows is better, faster, will startup fast,.

It was me who put the 3 months statement. There is no problem with the fact that these things require work and work takes time.

Then there is a target audience called ‘citizen’ developer’. People without an admins knowledge. For everyone and especially for a less tech-savvy audience, those incompatibility issues must be clearly advertised at the places the go to look. Otherwise they get caught between Apples’ and FMI’s marketing steamrollers who both say: just use it, just go for it. Its all easy and hassle-free.

Well, at times it is not, because of the compatibility issues. To be clear: the problem starts with the OS vendor. FMI has limited power over this. But: the right information at the right time at the right place prevents people from getting trapped and is good customer care. Again for a point of perspective, Microsoft broke their own software as per my original post. Their own update broke their own software and their response and eventual resolution was that a resolution would be released in 2-months.

In other words, anyone using their own software, that they broke, had to go without for 2-months. Thank goodness the community within the above link saved the day.

FileMaker are at the behest of Apple, who keep changing things without any continuity consideration, which has always been the case. It is ironic that we have no Windows compatibility issues. By the way, this was delivered today and I’ve already found a really good use for it:. We’re introducing a new syncing model for sharing calendars in Outlook for Mac. These changes will bring improved reliability and performance of calendar sharing in Outlook for Mac based on the use of REST technology.

This message is associated with Microsoft Roadmap ID: Older hardware? VMware ESXi 6. Many OS options there! And some older Macs can support various Linux distros – great tutorials a Google search away. I really appreciate all the discussion that this has generated. Yes, it started out as a rant because I wanted the discussion to start and was hoping for exactly what has happened. Generally, a very civil discussion on the state of things and others’ frustration with the delay in the updates.

I have read each and every response, and I have been thinking about them all weekend through today. I have come up with a few things that I would like to throw out for consideration by the community and FMI if you are reading this.

I’m just thinking about FileMaker for the next 20 years. I think as a community we need to keep an eye on FileMaker Today, Next Week, Next Year and when we build solutions for our clients, how long we can make them work and last. Until then I will sleep well, thinking about your post.

I’ll report back. This is one of the great benefits of going to DevCon. You can sit and talk with people like Clay one of the primary developers of the Draco engine , and other engineers. You can hear about the vision, what they are working on, and also as important, why they are not working on other things. This year, it was talked about, the underlaying technology. They are make a large shift. The idea is that they can switch out the technology under the hood, and nothing changes for us.

But it allows for both performance, and faster shifts when technology changes. It’s a long term plan. One similar to other areas of the platform that have already seen massive under the hood changes. We are already starting to see the benefits of changes like that. We will also see more as new stuff is introduced into the platform. The development methodology is not terribly relevant to the product. FileMaker’s testing process is fairly extensive.

That is the reason it takes so long. They do the beta testing, and go through the whole process. Then when the gold master is updated, they do it again. And when the final shipping release happens, they do the process again. That would have caused some serious for many software platforms. And this Knowledge Base article many versions!

This is all useful advice and very helpful – but aren’t you spending your time on somehow fixing something that is clearly on FMI’s plate? As an Apple subsidiary they should have fixed that ready for the Mojave release – it can’t be that difficult. And not only for FM17 as indicated in the press release posted by FileKraft but also for previous versions. I’m running There is a caveat though: The operators vanish again after some time; I could not figure out yet whether there is some “logic” in this.

So the dialog box size and position has to be reset over and over again. Let’s hope for a proper fix of that in the next update. Check and see if this is consistent with all solutions. I have an issue where the calculation editor shows up blank with button bars or trying to define an auto calc but only in one solution and only on Mac pro running mojave.

I have a bizarre problem with FMP 17 and Mojave. When I open the script editor, nothing displays when I select a script. The script steps editor simply shows “No script selected. The problem seems to be with outdated Works plugins. Time to download new versions, if available. Has anyone run their custom-signed app that they sell outside of the App Store through Apple’s new Notarization process for Mojave?

This site contains user submitted content, comments and opinions and is for informational purposes only. Claris may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Claris can therefore provide no guarantee as to the efficiency of any proposed solutions on the community forums.

Claris disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Claris Community Use Agreement. Search Loading. Register Login. Report a Product Issue. View This Post. July 1, at PM. Importing from from spreadsheet. Crash when creating new buttons in layout mode.

The FMP file is Too much work just to do FMI’s homework! Forward that to OWC. That would be interesting. Benjamin Fehr, Thank you for reporting this! Thank you for contacting OWC and please have an awesome day! Yes beta 3 18Ag is the latest. Is anyone else having the same issue? I am sure they already have something in the works. Sent from my iPad. Speaking of Mo NDA to send in as email to: forumsupport filemaker. I’m running Mac Limited resources.

Simple fact, FileMaker would need to devote countless hours to testing and refactoring code to work with some aspects of Mojave. Only to have that work thrown out the window when the next beta drops and have to start over. Since June, they have had at least 10 Betas drop as of the end of August. Being an Apple subsidiary. This doesn’t give FileMaker any specific advantage. It doesn’t.

I talk to the FileMaker people at DevCon. They get zero advantage here. That’s an Apple thing, not some failure on the part of FileMaker. Waiting for compatibility fix. FileMaker is not, by far, the worst at getting a compatibility fixes in place. It would be nice if we had zero-day support. But it’s just not that simple. From a professional development and systems admin perspective, the installed technology will always be behind the shipping release by 3, 6, 12 months. Dear FileMaker Inc: Keep in mind that ‘Mojave’ does not necessarily mean “voluntary update from an impatient existing user”; it could perfectly be a new FileMaker user who just own a brand new Mac; or an existing FileMaker user who had to buy a new Mac because the existing was dead.

Are you FileMaker Inc? I just am very diligent about reading. It is the 5th time i access and read it. My last comment, just a citation afterward you will have the last word, i promise : “There are known stability issues with FileMaker Server 17 with macOS Mojave Fred CH wrote: I would bet the contrary : Apple is very experimented in this game.

So would I. Benjamin Fehr wrote: Be aware that Apple Inc. Joshua Ormond wrote: I’ve been listening to a number of podcasts, including the MacAdmins podcast. FMPA 17? It was a clean install. No restore of any kind. Joshua Ormond wrote: A compatibility update is planned. And a wide array of templates, tools, apps, and training materials are at your fingertips on Marketplace.

To inspire your imagination, here are just a few things you can do with FileMaker Pro:. Your business spans the cloud, on-premise systems, and even devices.

And all of it has to work together for your business to thrive. Claris FileMaker Pro Unleash the power of the platform. Try now with a day FileMaker trial Buy now. Explore our Claris FileMaker purchase options.

FileMaker by the numbers. Technology for everyone. Using FileMaker Pro, any problem solver can: Drag and drop to create layouts. Use built-in templates and add-ons. Run apps on Windows and Mac. Right click the file and open it with filemaker Then if you want you can export your data from the trial version or buy the latest filemaker to continue using it. But you got me thinking of a different approach below and it worked! Thank you!! Success all around! Thank you. I was trying to open my old FMP14 files by directly double-clicking on them.

Then I went back to the FMP14 file on my desktop, and double clicked on it.