Error 438 Object doesn't support this property or method - Class Object with Dictionary

Question

_Background:

This is a follow-up question on this recent question I asked on how to return an array of Class module prop

Answer 1

As Tim correctly points out, Set is required here, because lst is an object.

What isn't clear, is why a missing Set keyword would cause run-time error 438, an error that's typically encountered with buggy late-bound code. The reason is, in a word, let-coercion: in the absence of a Set keyword, an assignment is an implicit Let (value) assignment.

If Class1 had a default member, dict(keyx) = lst would be let-coercing the lst object and storing the value returned by that default member in the dictionary.

Since Class1 has no default member (and the reference isn't Nothing), error 438 is raised (would be error 91 if lst was Nothing), because VBA is looking to invoke the member with a VB_UserMemId=0 attribute, and cannot find it.

The error 438 will occur on dict(keyx) = lst and tells me that the object (a Dictionary) doesn't support this Property or Method.

The object isn't the dictionary here, but your Class1 instance; the missing "property or method" is that object's default member, implicitly invoked through let-coercion. And since the member call is implicit, it's easily missed, and the error number/message is easily confusing.

Rubberduck (free, open-source VBIDE add-in project that I manage) fires an inspection result for Value Required here, that explains exactly what's going on:

In a context that requires a value type, the expression 'lst' of object type 'VBAProject.Class1' is used that does not have a suitable default member.

Object used where a value is required

The VBA compiler does not raise an error if an object is used in a place that requires a value type and the object's declared type does not have a suitable default member. Under almost all circumstances, this leads to a run-time error 91 'Object or With block variable not set' or 438 'Object doesn't support this property or method' depending on whether the object has the value 'Nothing' or not, which is harder to detect and indicates a bug.

In other words, that's one of many places where the VBA compiler defers to run-time instead of warning of something fishy at compile-time. Static code analysis is therefore the only way to reliably detect such bugs before they show up at run-time.