Share via

application.screenupdating gives runtime error 424

Anonymous
2017-07-24T11:24:33+00:00

I have never had this problem before but now I am getting this error on NEW spreadsheets that I create. Strangely enough, with exisiting files (even the xlsm/xlsb files, I do not have this error?

Why am I getting it all of a sudden

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2017-07-24T11:40:38+00:00

Do you do VBA programming?    I would look in the visual basic editor and then go to tools and then references.   You should have references to VBA, Excel, Office and OLE Automation.    Application should be a member of Excel.   When an object is being resolved, it starts at the top of the list so if you have a reference to something with an application member that is higher than Excel in the list this might be the problem.     (you can try unchecking that reference)

References are set at the workbook level.  So possibly your default template for a workbook has an errant reference in it.   First try creating a new workbook but use a specific template rather than the default workbook template.   If that workbook doesn't have the problem, then I would say that confirms that your default template has become "corrupted" in some way (maybe not truly corrupted but at least from a references standpoint). 

You would then need to create a new default workbook template. 

The problem could also be caused by a new addin you have added.   You can try starting Excel in safe mode (addins won't be loaded) and see if when you create a new workbook it doesn't have the problem.   Still it seems to me that if an addin is the problem it would affect existing workbooks. 

--

Regards,

Tom Ogilvy

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2017-07-24T16:06:40+00:00

    Thanks Tom... you are a star.  I was being a complete moron. I had copied and pasted some vb script from SAP which uses Application as an object In It's Startup Script... I just modified the sap object to be SAP_Application and my problem was solved😆

    Was this answer helpful?

    0 comments No comments