Simple Event Sample

using System;
namespace EventSample {
    class Program {
        static void Main(string[] args) {
            Metronome m = new Metronome();
            Listener l = new Listener();
    public class Metronome {        
        public event EventHandler<EventArgs> OnTick;
        public EventArgs e = null;                
        public void Start() {
            while (true) {
                if (OnTick != null) {
                    OnTick(this, e);                    
    public class Listener {
        public void Subscribe(Metronome m) {            
            m.OnTick += HeardIt;
        private void HeardIt(object sender, EventArgs e) {
            System.Console.WriteLine("HEARD IT");

Event in VBA

Windows are build upon three pillars: state, behavior and signal. They are implemented by property, method and events. Events are the way server (producer) signal to client (consumer) that some action has occurred and if desired, now is a good time to respond.
The server defines the events that act as the signature of the place holders and raise the events in the places that clients are permitted to insert their code.
From the client’s perspective, an event is an opportunity to respond to the changing state of an object. The following code is from VB & VBA in a Nutshell: The Language

  • Events can be declared and fired only from within object modules (i.e., Form, User Control, and Class modules). You can’t declare and fire events from a standard code module.
  • Events can be handled or intercepted only from within object modules. You can’t handle any type of event from within a code module. This isn’t really a limitation because you can simply include a call to a function or sub within a code module from within your event handler, to pass program control to a code module–just like you would write code in form and control event handlers.
  • The event declaration must be Public so that it’s visible outside the object module; it can’t be declared as Friend or Private.
  • You can’t declare an object variable as WithEvents if the object doesn’t have any events.
  • To allow the client application to handle the event being fired, the object variable must be declared using the WithEvents keyword.
  • VB custom events don’t return a value; however, you can use a ByRef argument to return a value
  • If your class is one of many held inside a collection, the event isn’t fired to the “outside world”–unless you have a live object variable referencing the particular instance of the class raising the event.
Server code: 
Public Event Warning(sMsg As String, ByRef Cancel As Boolean)
Public Property Let ClaimValue(dVal As Double)
   Dim blnCancel As Boolean
   If dVal > 100 Then
      RaiseEvent Warning("The Claim Value appears high", _
      If blnCancel Then
         Exit Property
      End If
   End If
   mdClaimValue = dVal
End Property
Client code: 
Private WithEvents oServer As clsServer
Private Sub cmdAdd_Click()
    Set oServer = New clsServer
    oServer.ClaimValue = 999
End Sub
Private Sub oServer_Warning(sMsg As String, _
                            Cancel As Boolean)
    Dim iResponse As Integer
    iResponse = MsgBox(sMsg & " is this OK?", _
                       vbQuestion + vbYesNo, _
    If iResponse = vbNo Then
        Cancel = True
        Cancel = False
    End If
End Sub