mrc's Cup of Joe Blog

Join us in exploring the world of modern development, evolving technologies, and the art of future-proof software

Year: 2025

Choosing a Web Query Alternative: One Consultant’s Methodical Approach

When IBM announced the end of Db2 Web Query for i, it caught many businesses off guard. Web Query was the go-to reporting tool for IBM i shops. Suddenly, those companies were left asking the same question: Now what?

Rick Flagler, an experienced IBM i consultant, heard that question from his clients almost immediately. They depended on Web Query for reporting and needed a reliable replacement that wouldn’t compromise functionality.

Rick approached the challenge with the precision you’d expect from a seasoned consultant. First, he created a “shopping list” of features that a Web Query replacement should include. He then dove into the landscape of BI tools built for IBM i, narrowing the field to those that ran natively and aligned with his clients’ needs.

From there, Rick didn’t rely on vendor claims or promises…he put each option to the test. He reviewed report designs, requested proof-of-concept demos, and evaluated each product’s ability to meet his criteria.

While I’m happy to say that his search led to m-Power, I’m just scratching the surface here. Rick wrote an article on the whole process, and goes into more details on his approach and criteria. You can read it here: “Life After IBM Db2 Web Query for i: Finding an Alternative.”

If you’re looking for a Web Query replacement, this article is well worth the read. It provides great insight into a thoughtful software evaluation process, what to look for in a BI replacement, and how an experienced consultant approaches this task.

To learn more about m-Power and how it can replace Db2 Web Query, check out this page: IBM Db2 Web Query Replacement

Internal Tools: How to Build Apps That Streamline Your Business

Imagine being stuck in an endless email chain…just to get a simple approval. Or worse, imagine wasting hours pulling data from disconnected spreadsheets only to realize it’s already outdated. 

The fact is, most internal processes are a mess.

Teams jump between tools. Spreadsheets do things they were never meant to do. Manual workarounds become the standard. Everyone knows it’s inefficient, but…no one knows how to fix it. Or, they’re just used to it.

That’s where internal tools come in.

Internal tools are custom apps built to solve problems inside your business. They help your team work faster, cut out repetitive tasks, and replace duct-taped processes with real solutions.

Better yet, they fit into your own infrastructure and unique business processes. When done right, these custom internal tools are invisible. They just work. They streamline processes and never get in the way.

The best part? Creating internal tools isn’t that hard. You don’t need a huge development team or a massive budget. With the right plan (and the right tools), anyone can build internal tools that make a real difference.

In this article, I’ll walk through how to do it. You’ll learn what works, what to avoid, and how to make internal tools a real advantage for your business. 

Sound good? Let’s get into it.

How to Build a Web-Based Dashboard (+ Video Guide)

Dashboards should make your life easier. Many don’t.

What happens? Some try to show everything at once…without really showing anything useful. Others take months to build and still don’t have the right data. Yet, making a change might take weeks. I could go on.

The good news? Dashboards have come a long way. They’re accessible from anywhere. They update in real time. And with the right tools, you can build one in a day—not a quarter.

In this article, you’ll learn how to build web-based dashboards in minutes that actually help people do their jobs. We’ll cover different types—like KPI dashboards, executive dashboards, and other business dashboards your different teams might use. You’ll learn some best practices, mistakes to avoid, and the best approach to development. 

Sounds good? Let’s get started.

How to create a custom, web-based scheduling calendar in 12 minutes

developmentLet’s be honest: There’s no shortage of web-based calendar tools these days. You’ll find dozens of off-the-shelf scheduling calendars that you can set up and deploy in your business.

The problem is, they’re all generic and every business is different. While these off-the-shelf scheduling applications might fit most of your needs, they won’t provide a perfect fit. They might do some things very well but lack key features in other areas.

But, what if you could create a custom scheduling application…faster than it takes to deploy a generic solution? What if you could create a data-driven, web-based calendar that was 100% tailored to your business…in a little over 10 minutes? It’s possible, and we’ve created a video to show you how it’s done.

Want to try it for yourself? Set up an m-Power Test Drive.

What is a CRUD Application (And How Do You Build One)?

Let’s talk about the unsung hero of business web applications: The CRUD application. They’re everywhere, whether you realize it or not. Your customer database? It’s a CRUD app. Your company’s inventory system? Also a CRUD app. Even when you’re posting updates on LinkedIn – you guessed it – you’re using CRUD apps.

But what exactly makes these applications “CRUD,” and why should you care? In this article, we’ll cut through the technical jargon and explore:

  • What makes an application “CRUD”
  • Real-world examples
  • Important tips for building them (the right way)
  • How to build CRUD apps quickly

Whether you aim to replace that aging system or build new applications, mastering CRUD apps allows you to understand your development project better and ultimately make more informed decisions about them. 

Sounds good? Let’s dive in.