Amazon Honeycode is a no-code development platform that frees us from the shackles of spreadsheets. With good intentions, we set out to make ourselves more efficient and organized by putting all of our important data and complex workflows into a bunch of spreadsheets. This process may have worked for a while, but most of us eventually find that we can't shoehorn our unique and challenging businesses into a grid. This is where a no-code development platform like Honeycode comes in to help with a big lift.
Imagine coding an app from scratch. How long do you think it would take you to develop and perfect it? How much effort do you think it would take to maintain and debug it?
Low-code development platforms negate these types of questions. You can use some code or no code to develop an app to improve your workflows. What's more, you can apply your technical and non-technical skills to design the app. Keep reading to learn about low-code and what makes for an excellent low-code development platform.
In a previous article, we chatted about FileMaker error codes and made a point to emphasize the importance of keeping our eyes open during development. We have to be ever vigilant within the obscure areas of our solutions where things might break. Sometimes, we have to push our solutions to the brink in the hopes of revealing a weakness that may have otherwise gone unnoticed. We also took a look at a few techniques for trapping errors and then organizing them so that we can deal with them appropriately. This post will explore a new tool that Claris gave us a few versions back called Set Error Logging. This tool allows us to take error trapping to a whole new height.
The Claris FileMaker Platform makes it easy for us to develop functional custom applications. We can move data from repeating fields and manage and customize images in FileMaker applications. It's also relatively easy for us to identify errors, but we have to know how to organize and interpret FileMaker error codes. If we learn when and how to leverage specific tools that FileMaker provides to troubleshoot bugs within our apps, we can avoid issues and frustrations down the line.
Identifying and capturing errors within our FileMaker applications are an essential part of the development process and it can feel a bit like a roller coaster ride. When we create an app that makes our jobs easier, we want to make sure that it does the right things effectively and reliably. That's why having a solid understanding of the potential error codes we might encounter and how to resolve them successfully is so important. In this post, we'll deal with the highs and lows of fool-proofing our FileMaker apps by maneuvering through conventional errors and exploring some common places where bugs tend to crop up.
If you've been around the FileMaker world as long as we have, you remember back when FileMaker Server 5.5 was released. One of the most remarkable aspects of that release was that it not only ran on Windows and macOS but also on Linux. FileMaker Server 5.5 was the last of the pre-7 servers and the last of the Linux versions...until now. Of course, that isn't entirely true because Claris has been using a Linux version of FileMaker Server on all of its Cloud services (both AWS and the current offering) since 2015. This Linux Cloud version wasn't available to the on-premise users but that's no longer the case. We think it was worth the wait because it opens up a lot of deployment options and some administration benefits.
The use of technology has expanded massively in the last few years. Mobile apps, smart devices, and the Internet of Things (IoT) mean that even the most mundane devices now run some form of "software." According to the U.S. Bureau of Labor Statistics, employment statistics reflect this with the growth of job opportunities for software developers, at 21%. We are on the brink of a developer shortage, and citizen developers could be vital to keeping businesses moving in the modern world.
This year marked the 25th anniversary of the FileMaker developer conference, the annual event where users learn and connect. The Support Group has been around for every one of them. However, this particular event was different from the rest, not only because it was hosted virtually, but also because Claris has shifted its focus from technology tools to business solutions. Claris even changed the conference name from DevCon, as in Developer Conference, to Engage to adequately reflect their attention on problem-solving. To that end, this year's conference was centered around how the different components of the Claris platform work together to provide people with solutions to their workflow challenges. These connections extend beyond the FileMaker platform, throughout the entire work universe, whether on planet Salesforce, nebula QuickBooks or galaxy MailChimp.
When you're running a business, every dollar counts. And every second counts. That's why running your business as efficiently as possible is so critical.
Fortunately, that's where the Claris FileMaker software development tool comes in.
So, what is FileMaker exactly? And how can you use it to improve your business operations?
Here's a rundown on what FileMaker is and how to use it effectively for your organization.
Let's jump in!
There's always room for improvement and that certainly applies to custom app development. We've discussed some of the things to watch out for when designing our custom FileMaker apps, such as how to deploy them efficiently when we access FileMaker remotely and improve the performance of record creation and modification. Mitigating these bottlenecks alone can transform our trusty old commuter cars into the hot rods we've always dreamed of. But even the best-oiled machines might need some internal reengineering from time to time to continue humming down the road.
In the previous article, we chatted about speeding up record creation and modification within our FileMaker applications. As we said, there's no one size fits all way to make an exotic supercar out of a minivan. However, there are ways to make that minivan corner smoothly and stop quickly and maybe even take off from the line like a dragster.
In this article, we're going to focus on ways to mitigate bottlenecks when we access our FileMaker apps remotely. Due to the pandemic, many of our users are accessing hosted apps from home. Of course, we do this over the internet, also referred to as a Wide Area Network (WAN). When we connect to the network at the office, that is typically a Local Area Network (LAN), which usually offers faster speed than a WAN.
