Me is a reserved name (you can't have a variable by that name) that refers to something that can only exist at run-time in a procedure's scope: the current object. Under the hood, when you make a member call to
DoSomething against a
Class1 object, the call goes essentially like this:
Set obj = New Class1 Class1.DoSomething obj
DoSomething looks like this in VBA:
Public Sub DoSomething() End Sub
But VBA sees it like this:
Public Sub DoSomething(ByVal Me As Class1) End Sub
Me an implicit locally-scoped
ByVal parameter of type
Class1, and inside the
DoSomething scope it holds a reference to whatever object the caller is currently using.
- Code Review 74k 74k 1717 gold badges181181 silver badges450450 bronze badges
- Stack Overflow 65.4k 65.4k 88 gold badges9595 silver badges208208 bronze badges
- Meta Stack Exchange 7.6k 7.6k 22 gold badges2626 silver badges5151 bronze badges
- Software Engineering 1.6k 1.6k 1616 silver badges3030 bronze badges
- Database Administrators 884 884 22 gold badges77 silver badges1414 bronze badges
- View network profile
Top network posts
- 123 Down with FizzBuzz... LOL
- 104 Is VBA an OOP language, and does it support polymorphism?
- 61 Interview coding test: Fizz Buzz
- 54 Implementing String.Format() in VB6
- 54 Are there disadvantages in putting code into Userforms instead of modules?
- 53 Unit of Work and Repository with Entity Framework 6
- 52 What are the fantasy secret hats you'd wish to get?
- View more network posts →