Excel Find / Command-F crashing on Mac Tahoe (Office 2019 / Excel 16.78) – anyone else?
Excel Find / Command-F crashing on Mac Tahoe (Office 2019 / Excel 16.78) – anyone else? Mac mini + Tahoe 26.5. Excel 16.78 (Office Home & Student 2019). Problem started after recent Tahoe update. Classic Find is behaving badly and often crashes Excel. Workflow: click/select a column Edit → Find → Find… or Command-F search for text or email fragments (ex: "kristin" or part of an email) Excel may crash or Find becomes unusable Things already tried: full Excel reinstall blank workbook test new macOS test user Office container reset / plist tests preference resets same Tahoe version confirmed Upper-right Microsoft Search appears, but that is not equivalent to classic worksheet Find for email-column workflow. Question: Is this a known Tahoe / Excel 16.78 Find bug or Search-routing issue? Has anyone fixed this or seen it resolved with a newer Excel build or update?
new 'card version' for cell phone viewing
I tried this on a sheet yesterday, and almost immediately regretted it. Not only did I have to mess around with the sheet when I went to my desktop, it appears to have locked me out of features I need - like especially merging cells. If any of the developers can help me get back my merge cell feature I would really appreciate it!
Excel App Builder: Should Excel Support Turning Workbooks into Standalone Low-Code Applications?
Excel has been much more than a spreadsheet application for a long time. In many organizations, Excel is already used as an informal low-code development platform. Advanced workbooks often contain not only data and formulas, but complete domain-specific logic: calculation models, planning tools, dashboards, input forms, reports, simulations, administrative workflows, and sometimes even small internal business applications. This is one of Excel’s greatest strengths. It allows domain experts, power users, analysts, engineers, teachers, consultants, and small businesses to build working tools without becoming full-time software developers. However, there is a structural limitation: the final product usually remains an Excel workbook. That creates several problems: the user needs a compatible Excel installation, macro security and Trust Center settings can block functionality, formulas and business logic are difficult to protect properly, distribution and updates are not as clean as with real applications, workbook-based tools often look less professional than standalone software, user interface, data, and logic are often mixed together in the same file. I believe Microsoft could turn this existing reality into a major strategic opportunity. Core proposal: Excel App Builder / Excel Runtime My suggestion is an official Excel App Builder or Excel Runtime. The idea would be to allow selected Excel workbooks to be packaged as protected standalone applications. Excel would continue to serve as the calculation, data, and automation engine in the background. The end user would not necessarily see the workbook itself. Instead, they would interact with a clean application interface: input forms, buttons, dashboards, charts, reports, controlled tables, and export options. Possible output formats could include: Windows apps, web apps, Teams apps, SharePoint apps, mobile-friendly internal tools, protected specialist applications. This would not replace Power Apps. In my view, it could complement Power Apps very well. Excel could remain the place where fast domain logic, calculations, prototypes, and models are created. Power Apps, Dataverse, Azure, and the wider Microsoft ecosystem could then support larger, scalable, enterprise-level workflows. In other words: Excel could become the natural entry point into Microsoft’s low-code ecosystem. Why this could matter strategically Excel already has an enormous “hidden developer base”: people who are not traditional programmers, but who build useful tools with formulas, tables, Power Query, Power Pivot, VBA, Office Scripts, and now AI assistance. This is a unique market position. Many of these users would not start with C#, JavaScript, Python, or a full application framework. But they already start with Excel. They already build the logic there. The missing step is a professional way to package, protect, distribute, and update those solutions. An official App Builder could: strengthen Excel’s long-term relevance, differentiate Excel from simpler spreadsheet competitors, create a stronger bridge between Excel and Power Platform, give power users a professional deployment path, create new commercial licensing opportunities, reduce the need for fragile VBA/UI workarounds, make Excel-based tools more secure and maintainable. Example use cases A small engineering office creates a technical calculation workbook and exports it as a protected customer tool. A school or university builds a grading, diagnostic, or planning tool with Excel logic but provides staff with a clean app interface. A small business turns an Excel-based quotation calculator into an internal sales app. A finance department packages a planning model as a controlled scenario tool for managers. A consultant builds specialized calculation tools and distributes them professionally without exposing the workbook structure. These are not exotic scenarios. Many people already build this kind of logic in Excel today. The difference would be that Microsoft could provide an official, safe, and professional deployment path. Supporting features that would make this stronger 1. Modern UI layer for Excel-based apps Excel-based applications would need a modern interface layer: forms, dialogs, navigation pages, buttons, card layouts, dashboards, responsive views, mobile-friendly layouts, role-based views, binding to cells, tables, named ranges, and data models. This would create a clearer separation between data, logic, and user interface. 2. Protected workbook logic A professional app export would require strong protection options: hidden formulas, protected named ranges, protected scripts or macro logic, defined input areas, digital signing, controlled editing, update mechanisms, possible licensing controls for commercial distribution. 3. Formula cells with controlled manual override One frequent Excel problem is that users overwrite formulas. A useful new cell mode could be: default formula + optional manual override The cell would keep the original formula internally but allow a controlled manual exception value. Excel could show whether the formula is active or manually overridden. This would remove many helper-column and VBA workarounds in planning, pricing, grading, budgeting, and technical models. 4. Native database layer inside Excel Excel is widely used as a database, even when that becomes fragile. A native database layer could support: primary keys, relationships between tables, required fields, validation rules, change history, duplicate detection, form views, simple queries, optional cloud synchronization. This should feel like a natural extension of Excel tables, not like a separate database product. 5. Multidimensional workbook models Many workbooks use separate sheets for months, locations, versions, departments, or scenarios. This often creates duplication and maintenance problems. Excel could support native dimensions for tables and models, for example: time period, location, scenario, version, department. Formulas, charts, dashboards, and PivotTables could become dimension-aware. This would be especially useful for financial planning, controlling, simulations, scientific models, and project planning. Why now? AI is changing how people build with Excel. Copilot and other AI tools make it easier for non-programmers to generate formulas, scripts, models, and structured workflows. That means more users will be able to build complex Excel-based solutions. But if AI helps users create more advanced workbooks, the next logical question is: How can these workbooks be safely packaged, shared, protected, and used as real tools? An Excel App Builder could be the answer. Possible first step This does not need to start as a massive platform. A realistic first version could be experimental: selected workbook ranges, simple input forms, protected formulas, dashboard view, Windows or web runtime, export as an internal app, optional Teams or SharePoint integration. It could even begin as an Excel Labs / Microsoft Garage style experiment to test demand and gather feedback from power users, developers, and organizations. Core question for the community Excel is already used as a hidden development platform. Should Microsoft make this official? Would an Excel App Builder / Excel Runtime be useful for your organization, clients, or internal tools? Which feature would matter most in a first version? protected workbook runtime, modern UI layer, formula override cells, native database layer, multidimensional models, Power Platform integration, commercial app distribution? I would be very interested to hear how other Excel users, developers, MVPs, and Microsoft product people see this idea. In short: Excel already allows millions of people to build domain-specific logic. Microsoft could turn that strength into an official, secure, and economically attractive low-code application platform.
unpivot data and handle merged cells without using Power Query (Unpivot_Toolkit)
Hey, guys!! I’ve been working on a set of functional Excel Lambdas to solve a common headache: transforming "Wide" human-readable data into "Long" database formats without having to open Power Query every time. =UNPIVOT_PLUS(table, [no_of_cols], [no_of_headers], [attribute_names], [value_name], [remove_errors], [remove_blanks],[pad_blanks_with],[pad_errors_with]) Don’t worry about the full list, most use cases only require 5 arguments. I've included a table of default values at the end. Merged Cell Support: Automatically handles fill-down/fill-right logic for merged headers/columns. Bonus Helper: SPLIT_INJECT =SPLIT_INJECT(array, target_indices, delimiter, [ignore_empty], [match_mode], [pad_with]) It targets specific columns, splits them by a delimiter (like TEXTSPLIT), and expands the entire table horizontally while keeping all other columns perfectly stable. Optional arguments match TEXTSPLIT defaults. Feel free to tear this apart or adapt it for your own edge cases. I’d love to hear how you end up using it! You can grab both functions from my GitHub Gist https://gist.github.com/Medohh2120/f8553c149684e39bb499249e39f01017 File with use cases https://1drv.ms/x/c/6c310c8fd1669a94/IQCscpo3yh7jR5XdGZe2AQGyAf4-vCd8K6BvLZQgrP2V8Oo?e=gPdbOd Argument Description Default Behavior table The array or range of data to unpivot. Required argument (no default) [no_of_cols] Fixed left columns to keep as identifiers. 1 [no_of_headers] Top rows used as headers, handling merged cells. 1 [attribute_names] Header name for the unpivoted attributes . "Attribute" [value_name] Header name for the unpivoted values. "Value" [remove_errors] Excludes grid rows with formula errors. FALSE [remove_blanks] Removes grid empty cells and empty strings. TRUE [pad_blanks_with] Value to substitute for empty cells. Leaves cell blank [pad_errors_with] Value to substitute for errors. Leaves error as-is
Conditional Formatting or a Specific Filter Rule
Dear Experts , I have a data like below:- here the Column-O, txNumber can go from 1,2,3 (txNum=2 and 3 means a Retransmission), I want to filter all the pairs for all Transmissions and their corresponding Retransmissions ( either by coloring them all using a conditional formatting) or using a specific filter Rule. How to identify the Transmission and it's corresponding Retransmission for a Specific HarqId( say for dlHarqProcessIndex ==7, the blue color Row-37 is my 1st transmission(txNumber ==1) for the dlHarqProcessIndex==7 with a tbSize of 852696, and adaptRetxStatus == NOTACTIVATE, and it's corresponding 2nd transmission( Retransmission , txNumber==2) Row-45, tbSize remains same(as it's corresponding 1st transmission) in all retransmissions and adaptRetxStatus changes to "APPLY" for all retrans txNumber==2,3) and similarly for other pairs like for dlHarqProcessIndex==13. Attached is the Worksheet.
Excel returns incorrect answer to simple multiplication.
I'm saving a few favourite math examples, and ran into a problem - the last of the calculations came back with an incorrect answer. I'm using a simple =cell1*cell2 formula. It should end with 21. Please help I'm using android app. All cells formatted as numbers.
