If you have ever watched a VBA script crash the moment it hits a hidden tab, you already know the frustration this user describes. Their code is simple and sensible: go to cell A1, set zoom to 100 percent, repeat for every worksheet. It works perfectly until a sheet is hidden. Then it fails. The fix is not complicated, but the problem reveals something larger about how we build workflows in legacy spreadsheet tools. That is where our opinion comes in: this is exactly the kind of friction that should not exist, and it is exactly the kind of friction that an AI-native spreadsheet eliminates from the start.
The user's loop selects each worksheet before applying the actions. When a sheet is hidden, you cannot select it. The code errors out. The solution is straightforward: check each worksheet's Visible property before acting on it. A simple `If ws.Visible = xlSheetVisible Then` wrapper would keep the loop running smoothly. But that is a patch on a deeper design issue. Why should a hidden sheet break a formatting routine at all? In a modern data tool, visibility is a property, not a gate. You should be able to apply actions across all sheets regardless of state, or filter by visibility with a single parameter, not a conditional clause that has to be hand-coded every time. The user is not asking for much, they just want their formatting loop to ignore what it cannot see. That is a reasonable expectation, and it is one that traditional spreadsheet architecture fails to meet by default.
For our readers who maintain VBA-heavy workbooks, this is a familiar headache. You write a macro, test it on a clean file, and then it breaks on a real workbook because someone hid a reference sheet. You add error handling, then another exception appears. The workaround becomes its own maintenance burden. What this user's question really asks is: why are we still working around these constraints? The answer is that legacy spreadsheets were built for a world where data lived in isolated files and automation was an afterthought. Today, you deserve a tool where the logic matches the intent. If you want to format all visible sheets, the tool should understand that without your VBA needing to guess.
The practical takeaway here is twofold. First, the immediate fix for this user is to add a visibility check before the select and zoom commands. That will resolve the error today. Second, the larger lesson is that small, recurring friction points like this one signal a tool that is no longer keeping pace with how you actually work. When you find yourself writing the same workaround across multiple projects, it is worth asking whether the tool itself should be doing that work. An AI-native spreadsheet does not require you to script around hidden tabs. It understands context, applies actions intelligently, and lets you focus on the outcome rather than the edge case. That is the shift worth exploring.