How to force vba compile of worksheet code on worksheet.activate

Question

I have inherited maintenance many excel sheets that are used by many people in my company. Recently one user has started getting application-defined errors which do not occur on other computers. I've debugged on his machine, and they happen when a worksheet is activated. It only occurs on worksheets with VBA in the sheet, and where there is an error in an unused routine. eg.

option explicit

sub RunReport()
... 
Setup.Activate 'compilation error occurs here when debugging
'I assume that this is the cause of the application-defined error which occurs when not debugging
...
end sub

workbook named Setup

Option Explicit

.... other code    

Private Sub ListBox1_Initialize()'Listbox1 has been deleted from the sheet so this is never called
        Dim allReports() As String
        allReports = Split(ALL_LOCS, DELIM)
        ListBox1.list = allReports 'compile error here because listbox1 doesn't exist
    End Sub

I assume that there is a setting that is calling a full compile of the code when the worksheet is activated. I want to turn it on on my dev environment so I can investigate these issues locally.
Where can I find this setting? (I am using office 2013)

Edit: For clarifcation based on answers. Option Explicit is set at the start of the code. I have autosyntax checking and require variable declaration set on my dev setup that does not experience this issue.

Answer 1

The Option explicit on top of your modules forces a variable check, you can comment it if you don't want the variable check, or add it if you want it.

Note that this option can be added automatically in all new modules created, with a setting in the options:

VBE's Tools ► Options ► Editor ► Checkbox Require Variable Declaration

Answer 2

From my experience, errors sometimes occur in VBA on other machines when You use in Your code some commands specific to x86 architecture when other machine is x64 and due to the fact that You use references (in VBA Tools->references) that are not available on other machines. Last cause that I've met were different security settings, e. g. maybe Your code uses sth that requires access to vba object model (in Excel File->Options->Trust center->Trust center settings->Macro settings). So first of all I recommend to check the Windows architecture on the suspected machine. Then check the references that You use in a workbook. And at the end check the trust center settings. I think that it might be very probable that You will not get the same errors on Your machine as they might be specific to only one machine (e. g. different system architecture, some specific references or trust center settings).

If the error is caused by a specific line in the code I understand that, e. g. there are two users of woorkbook and one deleted a tab, to which Your code reference and that causes the error. So I think that maybe a good approach for You will be to manage error. You can use On Error statements in vba, e. g. You have code that fires at workbook open and it runs three procedures from Modules, so You can do sth like this:

On Error GoTo Procedure1Error

here run procedure one

On Error GoTo Procedure2Error

here run procedure two

On Error GoTo Procedure3Error

here run procedure three

Exit Sub

Procedure1Error:

MsgBox ("Procedure 1 caused fatal error. Code was not executed.) Exit Sub

Procedure2Error:

MsgBox ("Procedure 2 caused fatal error. Code was not executed.) Exit Sub

Procedure3Error:

MsgBox ("Procedure 3 caused fatal error. Code was not executed.) Exit Sub

End Sub

If You do not notify user about problems then You could use the just On Error resume next (Your code will continue to execute) but I do not recommend it.