If obj.val = "zzz" Then (and it's true even if "aaa" or "bbb"! ABSURD!!)

For some absurd reason, on my 2 years old Excel ("Excel for Microsoft 365 MSO (16.0.13127.21062) 64-bit")
the following "TEST" function go inside(!) the If... Then... generating the MsgBox, whatever test is done by the If,
while the current version of Excel (standard channel, 64-bit) correctly jumps to the "End If" bypassing the MsgBox instruction.

Does this happen with your Excel version too?
Is it a confirmed bug? (it seems very dangerous!)

Module Module1:

Please Login or Register  to view this content.

Class MainClass:

Please Login or Register  to view this content.

Class SubClass:

Please Login or Register  to view this content.

MacroBug.xlsm file, ready to test

Screenshot:
Immagine 2022-10-09 134432.jpg

I get a compile error here. I am not familiar with a subclass feature built into VBA. I do not have a SubClass option available in Intellisense when I write a Dim statement and when I click F1 for help on it I get a "Keyword not found" page. Perhaps you can give a little more explanation about that.

As Subclass error.jpg

I just corrected some typos. Can you please try to copy and paste it again?

I can't replicate the error.

I get the same compile error.

@mikerickson how are you not getting the compiler error I get?

The SubClass is another class object. So code is in 3 code modules called Module1, MainClass and SubClass

I do not get the compile error nor do I get the bug of the If test returning False.
But I don't have 64bit to properly test.

I don't get compiler error, anyway here is the xlsm file ready to test: MacroBug.xlsm

Screenshot:
Immagine 2022-10-09 134432.jpg

Originally Posted by 6diegodiego9

For some absurd reason

6diegodiego9, you have edited your original post at least 15 times since first posting. This causes a lot of confusion. I got a compile error because you specified "SubCls" and didn't say what kind of module it was, but much later you clarified that this should be a "Class named SubClass".

Please avoid editing a post after people have already responded to it. If you really must do so, then indicate exactly what you have changed.

Originally Posted by 6StringJazzer

6diegodiego9, you have edited your original post at least 15 times since first posting. ...

Yes sorry, my edits were just corrections to the SubCls - SubClass typos (causing compiler error to you) and other aesthetic changes to make it all more clear.

Originally Posted by Haluk

@6diegodiego9, this works; ...

I actually found two workarounds to the problem, like you did. However, I'd like to understand why it happens, to avoid repeating the same bugged(?!) code in future, on that 2 years old Excel.

Do you have the problem with my original code?

My code was simplified from a real case where I need the function as parameterized constructor, to create new (disposable) objects depending on parameters (that I pass to the function).

I need it to instantiate the obj using the function. Does it work (with the function) with your Excel version?

If the fact that you explained before was that I didn't instantiate the class, I don't understand because of two reasons:
- I wrote "Set obj = New MainClass" inside the called function, this is where I instantiated it
- the whole code works correctly (doesn't go inside the If) with my updated Excel, while works uncorrectly (go inside the If) only with my 2 years old Excel

My guess would be that it was a bug that was fixed subsequently, whether acknowledged or not.

Originally Posted by 6diegodiego9

So, should we avoid to use such a pattern in all distributed VBA code to avoid executing unexpected code without even getting an error? I am scared of this...

Working on that basis, you'd never write any code in case there was a bug in some version of Excel.

No, mine has no problem with the original code.

No I didn't, since the OP said he already had workarounds. I was merely addressing the issue of the bug (since the code should work, and does in 2016 and current 365, both Mac and Windows).

Strange, but this one works in my system;

Please Login or Register  to view this content.

Originally Posted by 6diegodiego9

all of my company of about 25 thousand people are using a similar version of mine: Excel for Microsoft 365 MSO (16.0.13127.21062) 64-bit.

What release channel are you on?

I think I'd be enquiring of your IT team as to why you are so out of date. There have been quite a few security updates since then.