Issues with Data Snipper and VBA in Excel? - BUG

Hi ​@ds55! This is definitely interesting. Agreed that just uninstalling and reinstalling DataSnipper isn’t the intended way for this to work!

In the past I’ve seen something similar occur when macros would unhide all sheets as part of the process they ran. Since DataSnipper does create internal sheets, then some data for those sheets got transposed. Can’t say with certainty this is what’s happening here, but do you know if the macro unhides all sheets by any chance?

If that’s the case then potentially including a snippet in your macro to re-hide such sheets could help. An example would be something like

Sub HideDataSnipperSheets()
    Dim ws As Worksheet
    For Each ws In ThisWorkbook.Worksheets
        If Left(ws.Name, 12) = "DS_INTERNAL_" Then
            ws.Visible = xlSheetVeryHidden
        End If
    Next ws
End Sub

Basically the whole expectation would be to update the macro to skip any sheet that begins with "DS_INTERNAL_" and ensure these are re-hidden afterward to avoid confusion or errors.

Let me know how it goes ​@ds55 and it might be a good idea to reach out to support if needed, but I’m curious if the above helps 😊

Thanks for your response! I actually don’t do anything with hiding sheets. A few sheets get deleted but they are named specifically in the vba code (not looping and deleting a lot of sheets).

The only other thing it does with sheets is opens other workbooks and copies a few over into the current one as well as creates a few too.

Do you know if there is a way to block data snipper from writing error/info messages directly into the excel file?

Oh I see ​@ds55 , thank you for clarifying.

As far as I am aware, the ways to “block” DataSnipper from writing error/info messages would be to block DataSnipper from writing entirely (for example enabling workbook protection, but then that would not allow DataSnipper to function at all).

Did you by any chance, as a just-in-case try to ensure the code skips all “DS_INTERNAL_" sheets to see if that solves the issue anyway?

I don’t know if I’d have other suggestions for something like this, so I’ll revert to maybe you sharing those with us via support so we can take a deeper look?

Again quite curious how this goes, so let me know ​@ds55 please 😁

Hey ​@ds55, did you ever manage to make this work?

​@Marios Morad I didn’t unfortunately. However I did find a workaround. I protected the original sheet that had the issue so it didn’t happen there. However datasnipper then started adding this to the header of a different sheet. I wrote into the vba code to rewrite the headers in at the end. It didn’t solve any root issue but it did make it so the user won’t notice the problem.

Thanks ​@ds55 , that’s an interesting workaround! I’ll bring it up internally as well, see if we can make things better on that front, but that still sounds like a useful way to tackle this 😊

Thanks again!