Mystery Application.Run call; Macro Unknown

[Sleeking]

Hi everyone,

I'm looking after some huge Excel apps made by someone who has left the organisation, which no-one else knows anything about..

This one simply falls down on an app.run call, custom error message is: "Macro 'sxlReadItems' does not exist."

The thing is, i've logged on to the departed person's account and have exactly the same problem running it from their account.

So, IS THERE ANY WAY IN WHICH I CAN GET A CLUE AS TO WHERE THIS MACRO LIVES? I notice that it does not have a prefix reference to an external workbook, (e.g. App.Run(Wkbk1!'sxlReadItems', arg2, arg3)) that is the confusing thing, and
I don't know of any add-ins which are missing. Does the prefix 'sxl' ring any bells?
Unfortunately the users of the app are in a different building so i can't just go over to see them, but I do believe they are running it every day without problems.

Snippet of code, not that it helps:

Private Function ReadItemList(sRangeName As String, filter As String, Optional sRtnMsg As String = "success") As Long
On Error GoTo err_msg
    Dim oData As Range
    Dim paramRng As Range
    Dim vBOptArray As Variant
    Dim lNumRows As Long
    Dim lNumCols As Long
 
    running True, "retrieving items for " & filter & "...!"
    Set oData = Range(sRangeName)
    '--- clear data
    oData.ClearContents
    '--- size range variable for column headings
    Set paramRng = oData.Offset(-1).Resize(1)
    vBOptArray = Application.run("sxlReadItems", filter, paramRng)
'More code here...
End Function

Thanks for reading

 

[Andrew Poulsom]

Welcome to the Board.

The macro should be in a General module in the workbook that contains the function you posted.

 

[Sleeking]

Hi Andrew thanks for posting.

I already searched the code for the string "sxl", with 'Search' set to 'Current Project' (i.e. all modules), which returned only the one App.Run call already shown.

So it's a mystery to me how this could ever have worked. Could 'sxlReadItems' perhaps reside in an xla which is not loaded I wonder?

I suppose this isn't really a standard question about 'broken VBA', but more a question about VBA detectivework!
Thanks

 

[Andrew Poulsom]

Yes, it could be in an Add-In that's not installed/loaded.