Here's a problem that should not exist in 2024: a user writes VBA code to automatically update a date when a cell is selected, and the macro still prompts for permission to run. The code itself is fine. The logic is sound. The failure is in the tool.
The user, Clear_Assumption9338, posted a straightforward request on a forum. They have a `Worksheet_SelectionChange` event that calls an `updateDate` subroutine. It works exactly as intended, except for one thing. The macro prompt appears every time, turning an automated workflow into a manual interruption. This is the kind of friction that makes people question whether their spreadsheet is working for them or against them.
What is happening here is a settings issue, not a code issue. In Excel, macros are disabled by default for security reasons. The user needs to enable macros in the Trust Center or save the file as a macro-enabled workbook (.xlsm). The prompt is Excel's gatekeeper, and it does not distinguish between a helpful automation and a dangerous script. That is understandable for security, but it creates a terrible experience for someone who just wants a date to update automatically.
The deeper point is this: when a tool requires you to fight its own safeguards to do something simple, the tool is not serving you. The user's goal is straightforward, select a cell in a specific range, and have a named cell reflect that value. No prompts. No clicks. No "are you sure?" The fact that this requires forum posts and configuration changes reveals a gap between what spreadsheets promise and what they deliver.
This is where the conversation about AI-native spreadsheets becomes practical. A modern tool should understand intent. If you want a cell to update based on a selection, you should be able to describe that intent in plain language, not debug event handlers and trust center settings. The user's problem is not that they cannot code, it is that they have to code at all for something this basic.
Our view is clear: automation should not be a hurdle. It should be the default. The user's experience here is a symptom of legacy design that treats every automation as suspicious. That mindset worked when macros were rare. It does not work when every knowledge worker needs to streamline repetitive tasks. The solution for Clear_Assumption9338 is to enable macros and save the file correctly. The better solution for everyone else is to use a tool that does not require that conversation in the first place.