Looking for:

– Filemaker crashing since Mojave update

Click here to Download

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

By joining Download. IObit Uninstaller. Internet Download Manager. Advanced SystemCare Free. WinRAR bit. VLC Media Player. MacX YouTube Downloader.

Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Windows Windows. Most Popular. New Releases. Desktop Enhancements. Networking Software.

Software Coupons. FileMaker Pro Free to try. Build a database tailored for your unique needs. Database software to manage people, projects, assets and more. Pro Evolution Soccer 12 demo Free to try.

Return to one of the most advanced soccer simulations with this demo for the upcoming PES BladePro Free to try. Add 3D effects to your images. FileMaker Pro International version Free to try.

Share information on a network, over the web, and in popular formats, such as PDF and Excel. HelpDesk Pro Free. Stock all the information on alerts and requests. FileMaker Server Free to try. Manage and share databases. Host your FileMaker Pro workgroup solutions. Recovery for FileMaker Free to try. Repair broken FileMaker Pro database files or retrieve data from the most damaged ones.

 
 

 

Claris FileMaker Pro – Join or Sign In

 

I then had it replaced with a OWC. All they stated is I should send new Report if problem still consists with Golden Master. How old was the original SSD? They do fail.

I had an internal OWC SSD but it melted after a year and left residue all over the inside of my 15″ MBP and another was defective on arrival but we didn’t realise it right away. No issues. I serious doubt Apple placed restrictions on installing Mojave on 3rd party SSD drives or that the beta damaged your drive.

In my 30 years of managing Macs, that really makes no sense to me, unless there was a faulty firmware upgrade.

An hourly backup on Time Machine should be more than enough for data integrity. In all honesty, i stopped buying anything from OWC. I’ve had too many issues with their gear over the years and their management has gotten a little too cocky for my taste. Success does that sometimes. In my last incident they made so many amateur mistakes that I gave up on them. Plus, their Thunderbolt-3 solutions are shit. Software RAIDs are cheaper to make and I’m sure it boosts their profit margins but if you ever have to do a complete rebuild, especially with a laptop, you’ll quickly learn that’s not the way to go.

That’s important when rebuilds can take a day or days with larger drives. Plus, hardware RAID are simply going to be more reliable since the software is fixed in the firmware. It just doesn’t run.

So leave your servers alone. Unrelated to Mojave, but I found the same hanging on ODBC imports when it was importing into a table where there were auto-enter functions on a field. I ended up having to import with no auto-enters and then manipulate the data. That has improved with the current version, but occasionally still happens. This was on windows platform. Don’t know if that is possibly related, but I thought it sounded similar, so I thought I’d mention it.

Both failed will not install. Yes correct FM No luck. You seem to have some other kind of issue. Did you upgrade from High Sierra to Mojave or did you do a clean install? I first did an upgrade and had weird issues. So I did a clean install and used migration assistant to restore from a backup. So I reinstalled over it, without erasing the disk, and it booted up fine. It seemed to be some kind of weird cache or permissions issues, which makes sense if your restoring from a backup with years of cruft on it.

The increased security measures probably conflicted with something. Do you have any third-party utilities installed?

For example, anti-virus software? If so, make sure those are all turned off before installing. If you are still having difficulty, contact our Technical Support department at toll-free North America. If you are outside of North America, contact the FileMaker office nearest you. I did a clean install of Mojave on a MacBook Pro. Re-downloaded FMPA We are trying to hold off buying any new machines until after October,.

Nothing official. Just the rumor mill. If we can hold off until October, and they release something worthy, we don’t have to buy 4 year hardware at brand new prices.

If they don’t, well, we don’t have a choice then. We have dozens of machines that are getting too old to run the most recent OS. I had an existing install of FileMaker 17 on HighSierra. Last night, I ran the update for Mojave. If run into anything significant I’ll update my comment. This appears to be a problem specific to your computer? Have you tried running a full Apple diagnostic on your computer?

Use internet recovery on your MBP to download and install Mojave directly from the internet. We need those operators. You can just type the text for the operators yourself. Oh, I thought they were non existent! OTOH, not everyone remember what operator does what. Your cheat-sheet is below. But honestly, the only symbol I’ve ever used this list for on a Windows machine is the return character, as I’m not sure there’s a way to do that from the keyboard.

Everything else is on your keyboard. It’s not I that needs a cheat sheet. I was referring to my clients. You can also copy them all from this page I wish it were that simple on Windows. I can enter the ascii code for the symbol itself, which works, but it’s not an easy or obvious one to remember. Maybe I’m the only person who knows that a return is ascii 13, so ALT is what I’ve always tried in the past and that doesn’t work.

I’ll have to try to remember ALT 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. We are forced to be on the latest OS with all of the new people entering.

Our workaround currently is to have them open a Windows Remote session to use FileMaker which they dislike using in Windows , but at least there aren’t UI glitches.

I think might be a problem that FileMaker is stuck in the Java world. I’m guessing those UI issues are related to Java windowing issues, or is that a bad guess? The individuals concerned are laboratory technicians using two of our more complex database systems hundreds of scripts, some quite long. We’re watching them closely incase we need to move them to 16 or 17, but so far it’s been okay. Just to offer a tiny datapoint. I’m somewhat puzzeled by the ‘community use agreement’, to be constructive.

So, having Mac-users to work with remote desktop to a Windows machine is a good and effective way to run FileMaker 17! We have customers who are happy to run FileMaker 17 on their Mac’s under mojave with the workarounds available resetting the dialoges, etc. Let’s do an example with Joe Doe, who has an issue with a software that costs him time to resolve.

After having this for three times, Joe writes to the local support, in a not so nice way. Support reads that and says ‘omg’, rephrases Joe’s mail and forwards that to the next level of support. NL support reads that and feels not so happy with the wording, does some corrections and sends that mail to the dev. Dev reads that mail and is somewhat confused, asking a colleague. Colleague reads it and says ‘oh, seems that it’s an user from europe, he want’s to say ‘hi”.

Plans are afoot to transition away from the Java environment over the next couple of releases. Clay mentioned it in one of his deep dive videos from DevCon. Server side I believe. Around the 4 minute mark. He indicated that Java and the Tomcat implementation framework. They are moving to Node. Truly maddening. So, great finally Apple releases new Mac minis.

Oh, and great they moved the goal post from November to December. An update is planned for FileMaker Pro 17 Advanced in the December timeframe to address these issues. An update is planned for FileMaker Server 17 in December The timing and scope of these updates are subject to change at the sole discretion of FileMaker, Inc.

Keep in mind, there is a lot under the hood to deal with for this Mojave update. It is not trivial. I agree it is a hassle to deal with, especially if you have to purchase new Macs. But the whole IT industry is having trouble with some of the changes. Even those companies that did have zero-day support have commented on the complexity and challenge of making the updates to work with Mojave.

Much of it is security changes. So there are a lot of behind-the-scenes approaches that no longer work. Finding ways to make them work are not easy. This is very much a case of FileMaker, Inc. We are getting the same thing from various vendors, not just FileMaker. That’s how the 2nd time they’ve changed it. I am starting to think that maybe I just move to Windows for all my development work except for FileMaker Go and just use my Mac for everything else.

What is the basis for this comment? I guess this discussion is going unnoticed by FMI. I had a setup with 4 27″ monitors. Two of those monitors were running on DisplayLink adapters. 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. When a new system version is released it is not when the clock started. It started when Filemaker engineers and Apple engineers collaborated and both companies knew that a change was coming.

I cannot imagine the number of hours that should have been spent on this collaboration. Even so, many things will never show up until the thousands or tens of thousands of users put the final release through the ringer.

But these things should be the semi obscure type of “when I stand on one foot, raise my left hand, and click in an edit box while whistling Even the one where working with formulas and having to reset the dialog boxes to get the operators back should have never been released.

It happens on way too many macs to be that obscure problem. So while I believe some bugs are going to be found, the amount of time Filemaker and Apple had to get it right started much, much earlier than the release date of either product. Long story short, the problem was with Windows 10, none of our clients’ internal or external IT departments assisted with any effect, the Microsoft community within a post similar to this came up with a temporary fix, and Microsoft’s response was that ‘we’ll fix it in a couple of months’ which they did and re-broke the temporary fix the community used to help their clients.

The point of this was that the whole responsibility fell on our shoulders as it was perceived as our problem.

The danger is, as this thread has highlighted, that this is a FileMaker problem and not an Apple or Mojave problem. Having worked alongside Apple for 35 years, I do feel FileMaker’s pain. This may be where some of my words have been missed.

And why I have a reputation. I definitely don’t discount the annoyance of the issues you describe. I’ve attempted to do 2 things in this thread. Clarify the state of the product.

I challenged the “unusable” part. That needed to be clarified for the many readers that may not have understood your objective.

Which clearly wasn’t intended as a rant, and the only reason the thread was allowed to continue. Overall, it’s been a great discussion. Identify the actual problems. We went a long time in the thread before we identified the problems. From a technical perspective, I want those annoying bugs fixed as much as the rest of you. When the bug is detailed, I can also recreate it, and add my samples to the issue reported. That helps the engineers get it fixed when we all do that, not just me.

I definitely have a higher pain tolerance than most people for certain things. However, that is not true of my primary development machine. I am VERY careful to protect that environment. I would not do anything to disturb that.

All testing for betas happens in a VM. Once all of the issues are worked out, only then will I update my primary development environment. I will use whatever version, FM and OS, works best for that. For me it is a Mac running High Sierra. But it easily could be a Windows 10 laptop. I have done, and do development on both. What would happen if my primary machine died? I would buy a new one.

I also appreciate all of the feedback people are giving. Create apps to manage contacts, track inventory, organize projects, and more. Build an app in just minutes and hours rather than days and weeks.

FileMaker Pro is a low-code tool with pro-code power. Using FileMaker Pro, any problem solver can:. Use FileMaker Pro to make the apps and systems you use every day even better. Work with your existing data to get started. FileMaker Pro comes with built-in templates to jump-start your creativity.

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.

 
 

Filemaker pro 12 advanced mojave free.filemaker pro 12 advanced

 
 
FileMaker Pro operating system requirements – all versions ; FileMaker Pro Advanced, Sept macOS Catalina ; macOS Mojave ; macOS High. If you have a manual process, automate it with Claris FileMaker Pro. Create apps to manage contacts, track inventory, organize projects, and more.

Leave a Reply

Your email address will not be published.