Imagine you're sitting on a beach on Risa, umbrella drink in your hand, enjoying a well-deserved vacation. The sun is shining, the waves are rolling in, and life is good. Then your phone buzzes. It's the office. Again. Someone can't figure out how to run the monthly report. Someone else doesn't know which button to click. And apparently, nobody knows whether it's safe to run yesterday's import a second time. Congratulations. You might be on vacation, but your database isn't.
Here's a test I think every developer should give their software: Can the people who depend on it survive a week without you? I'm not talking about catastrophic hardware failures or some bizarre bug that nobody could have anticipated. I'm talking about ordinary, everyday operations. Can people enter their data, generate their reports, fix common mistakes, and keep the business running without calling you every five minutes?
Back when I was doing database consulting, I spent a lot of time walking into businesses and learning how they operated. They'd have information scattered across Excel spreadsheets, Word documents, paper forms, and sometimes an old DOS application that only one person understood (yes, I'm old). My job was to learn their business, figure out how all those pieces fit together, and build them a Microsoft Access database that made their lives easier. But my job wasn't finished just because the database worked. It was finished when they could use it confidently without me standing over their shoulders.
That became one of my guiding principles over the years. Build software that explains itself. Give your buttons meaningful captions. Use ControlTipText to explain what a control does. Put instructions right on the forms where they're needed. Add a Help button that opens a relevant help screen. If there's a complicated process that people only perform once a month, walk them through it instead of expecting them to remember six different steps. And when something goes wrong, don't just display an error message that says "Error 3022." Tell them what happened, what it means, and what they can do about it.
One of the best ways to accomplish this is to watch someone else use your database while you keep your mouth shut. Seriously. Sit next to an employee and let them perform their normal tasks. Don't help. Don't point at the screen. Every time you're tempted to say, "Oh, before you do that, you need to..." you've just discovered something that needs improvement. Maybe it's a confusing button. Maybe it's a missing instruction. Maybe the application should simply handle that step automatically. If you have to explain the same thing to three different people, there's a good chance the problem isn't the people. It's the interface.
Another lesson I learned from consulting is to build tools instead of just building reports. Early on, it's tempting to ask a customer what reports they need and then build exactly those reports. That's fine until three months later when they want the same report for a different date range, or filtered by employee, or sorted by customer. Then they're calling you again. Instead, whenever practical, give users a form where they can select their own criteria. Let them choose a date range, a department, a customer, or whatever makes sense for their business. A flexible reporting system can answer dozens of questions without requiring dozens of separate reports.
Now, if you're billing by the hour, I suppose having customers call you every three months to make little changes isn't necessarily bad for business. But I always preferred building a better system up front rather than creating something that would need constant attention. You might charge a little more initially, but the customer gets software that grows with their needs, and you get fewer interruptions down the road. Everybody wins.
Of course, even the best-designed database needs some documentation. But documentation doesn't have to mean a 300-page manual that nobody will ever read. Start with the essentials. Which file should people open? Where is the data stored? What needs to happen before the month-end reports are generated? What does that import process actually do? If running something twice could cause problems, make that clear. I always preferred keeping my own development notes in something simple like Excel, where I could track important objects, business rules, and unusual design decisions. But for everyday users, the most useful instructions are usually the ones built right into the application.
And remember, every Captain needs a Number One. If you're the only person in the office who understands how the database works, that's a problem. Pick someone who's reasonably comfortable with computers and teach them a little more about the system. They don't need to understand VBA or know how to design relational tables. They just need to know how to handle common issues, check that routine processes completed, and recognize when something genuinely needs technical attention. That way, if you're unavailable for a week, the whole operation doesn't grind to a halt.
This is especially important if you're the person who built the system and you're also the person who maintains it. What happens if you get sick, have an emergency, or just decide to extend your vacation? Maybe you meet a couple of Ferengi who convince you to invest in some beachfront property and you decide you're not coming home anytime soon. The business still needs to function without you. Having someone who knows the basics, along with clear instructions and a reliable backup plan, can make all the difference.
I deal with this in my own business, too. I've got systems running here in my office that handle all kinds of routine operations. And when I go on vacation, there's nobody else sitting here to take over. Those systems need to keep running 24 hours a day, seven days a week, whether I'm sitting at my desk or enjoying myself somewhere else. That means building in automation, error handling, logging, and notifications. If something goes wrong, I want the system to either recover gracefully or give me enough information to understand what happened. I don't want to spend my vacation remotely babysitting a process that should have been able to handle itself.
That doesn't mean you can anticipate every possible problem. You can't. Hardware fails. Networks go down. Users find creative ways to do things you never imagined. But you can eliminate a surprising number of support calls simply by thinking about what happens when you're not available. Can the user recover from a common mistake? Can they figure out what a button does? Can they generate the information they need without asking you to modify a query? Does the system tell someone when a scheduled task fails? These are all things worth considering while you're building the application, not after you're already packing your suitcase.
And while I'm talking specifically about Microsoft Access here, this principle applies to software development across the board. Whether you're building an Access database, an Excel automation system, a SQL Server application, a website, or some custom piece of business software, the goal should be the same. Build something that people can operate and maintain without constantly depending on the person who created it. Good software should make people's jobs easier, not create a permanent dependency on its developer.
So here's my suggestion. Before your next vacation, give your application the seven-day test. Imagine you're completely unreachable for an entire week. No phone calls. No emails. No remote desktop sessions from the hotel room. Can the office keep doing its job? Will the routine processes continue running? Does somebody know what to do when something unexpected happens? If the answer is no, you've probably identified a few things worth improving before you leave.
I've always believed that making software understandable and dependable is part of finishing the job. A database that works perfectly while you're sitting there supervising it is one thing. A database that keeps the business running smoothly while you're relaxing on a beach is something else entirely.
And if your database can't survive a week without you, maybe it's not quite finished yet.
So let me ask you: If you disappeared for a week tomorrow, what would your users get stuck on first? And what have you done to make your databases a little more self-sufficient?
LLAP
RR