Excel macro VBA issues
Hey guys. - I wrote a macro, which contain other macros using Call orders. If I running the macros separately everything ok, from the main macro one of them didn't running it's like it skipped from the list. Reason unknown. -On running I can see 4 application window get visible, and those didn't connect any kind of application. Also a Clipboard error message get visible, but I get a Clipboard cleaning macro, which several times cleaning the Clipboard, so it can't be. It's like a hack, or something which I don't recognize. - One a sheets called Total, I can't use the built in group function and can't collapse the selected section so the project I working on lost functionality. I didn't make any change on that side, but previously it was useable. Thanks for help in advance. Cheers. Zsolt
EXCEL FORMULA HELP
I need help. I have attached the sheet I'm working on. I need to pull the data in column B (CLIENT) from the MAIN sheet to the respective individual sheet based on column E (PREPPER). For example, if the data in B4 says 'Jason Smith' and E4 says 'Jon'; I need it to go to the JON sheet in cell B4 but not show up on sheets JANE or MARLA. Help please!! Thank you! :)Excel’s "Very Hidden" Sheets… even the Unhide menu can’t find them
Just learned that Excel has a "Very Hidden" sheet state. Unlike normal hidden sheets, these don't show up in the “Unhide” menu at all. To create one: Press Alt + F11 to open VBA. In the Project Explorer, right-click a sheet → Properties. Change Visible from -1 (Visible) or 0 (Hidden) to 2 (Very Hidden). Now, only VBA (or the Developer tab) can bring it back. Perfect to keep things tidy or prevent accidental edits. Did anyone else know about this ninja-level Excel feature?
Setting Default Worksheet using Office Scripts
I'm working on an office script for Excel that generates the file as I want it, but for some reason, the file automatically opens up to the last sheet in the lineup instead of the first. I've tried a few methods like .activate() but they don't seem to work; only opening the file manually, switching to the first sheet, and saving does. Switching sheets also doesn't show up in when recording actions. Is there a command or method to make sure the file automatically opens up to the first sheet after my script is done setting up the document?BUG REPORT: Microsoft Excel Table Versioning Incompatibility Breaks Macro Logic
Excel tables now silently behave differently based on internal "versioning" (version 1 vs version 2), which is undocumented, invisible to the user, and directly breaks macros that previously worked across all sheets. There is no native method to identify which version a table is using, and users receive zero warnings when behavioral changes cause critical automation failures. Impact: .ListRows.Count and .ListRows(lastRow).Range.Delete fail inconsistently depending on the hidden version type Developers are forced to rewrite macros—not for logic reasons, but to compensate for Excel silently violating expected object behavior No version flag exposed in the UI, VBA, Power Query, or formula metadata Breaks trusted workflows for trainers, dashboard builders, and automation developers—especially during live sessions or instructional demos Forces users into non-consensual, destructive workarounds like converting the table to a range and rebuilding it from scratch. This should never be necessary. A user should not have to destroy a structured object to restore its usability. Repro Steps: Create a table via "Insert > Table" (defaults to version 2 silently) Copy data from older workbook sheets (some revert to version 1) Run macro using .ListRows(lastRow).Range.Delete Logic fails, errors, or behaves inconsistently Only workaround: convert table to range and rebuild—which is professionally unacceptable Temporary Workaround: On Error Resume Next With ActiveSheet.ListObjects(1) Dim lastRow As Range Set lastRow = .ListRows(.ListRows.Count).Range If Trim(lastRow.Cells(1, 1).Text) = "" Then lastRow.Delete End With On Error GoTo 0 Call to Action: Microsoft must publicly acknowledge the undocumented and silent divergence in structured table behavior between internal “version 1” and “version 2” implementations. This regression has: Broken established VBA logic Caused hours of untraceable macro failures Forced users into destructive workarounds Undermined trust during live instruction, client deliverables, and advanced workflow design Provided no way for users to identify table version—this is unacceptable We demand: Full disclosure of structured table version differences—what changed, why, and when Visible version metadata in Excel’s UI, VBA object model, and Power Query Behavioral standardization across workbook sources and creation methods Permanent removal of forced workarounds like converting tables to ranges just to restore row deletion logic Public bug tracking, resolution timeline, and community updates If Microsoft cannot provide these answers, then Excel structured tables must be considered unstable containers for automation. Developers and trainers cannot build trusted systems on invisible rules and undocumented regressions.
