This is a great example of someone trying to solve a real problem with the tools they have, and it highlights exactly where traditional spreadsheets fall short. The user here is not asking for a miracle; they are asking for a way to connect files, search by ID or name, and jump to the exact row in another workbook. That is a reasonable, practical need. And the honest answer is that Excel was never designed to do this well. You can hack it together with VBA, complex hyperlinks, and a lot of patience, but the result will be brittle. One moved file, one renamed sheet, and the whole system breaks. That is not a solution. That is a maintenance trap.
What this user is describing is a relational data problem dressed in spreadsheet clothing. They want a search interface that acts as a central hub, pulling information from multiple source files and directing the user to the correct record. In the world of traditional spreadsheets, this requires custom scripting, careful file management, and a tolerance for constant troubleshooting. The user admits they are "above average" with Excel and willing to learn VBA. That willingness is admirable, but it should not be necessary. The tool should handle the connection. The user should only have to define what they want to search and where to look.
We believe the better path is not to build a Rube Goldberg machine inside Excel, but to explore a tool that treats data as connected by default. Imagine a spreadsheet where you can define a lookup that reaches into other files automatically, where clicking a name opens the source document and highlights the row without a single line of VBA. That is what an AI-native spreadsheet can offer. It understands the relationships between your data and surfaces them without requiring you to become a part-time programmer. The user's goal is to save time for their coworkers. The most effective way to do that is to choose a platform that already thinks in connections, not one that forces you to build them from scratch.
The term the user is searching for is "cross-file lookup," but the real question is whether the tool they are using respects their time. If you find yourself writing VBA just to link two spreadsheets, you are working against the grain of your software. Our take is straightforward: stop trying to force Excel to be a database. Instead, find a spreadsheet that was built to be one. Your coworkers will thank you, and you can spend your energy on the problems that actually need your expertise.