VBA compiler suddenly requiring application. or worksheetfunction. expressions

Does anybody know why this is the case?

For instance, it usually takes for granted you're talking about the ActiveSheet but suddenly it required me to say Application.Activesheet or it wouldn't compile.

today I found one of my simple convenience macros that trims a cell required me to specify Worksheetfunction. It would compile, it just wouldn't do anything.

I don't know why and I guess that's what I'm asking, but I know when. it did happen shortly after I created a convenience macro to one click delete the active worksheet. I thought maybe this screwed up some logic in the system. Note it still requires this even the next day after rebooting and all that, so it definitely persists. I also added a reference library but that was after the fact. I added Microsoft Scripting Runtime. I think it has to do with the macro that deletes the active worksheet literally one line of code

Please Login or Register  to view this content.

Please Login or Register  to view this content.

Please Login or Register  to view this content.

.
He lives !!!

Not sure. I haven't thought about this lately but it's still something I'm curious about, for later. As a best practice, I've been typing out the full expression for everything (e.g. application.activeworkbook..). Who knows what will happen on someone's local machine at some point, but this is something I'll come back to if I ever get a chance.

VBA is deeper than you thought. It's obviously not a hardcore language like C++ or whatever, but it goes deeper and deeper. I'm constantly learning new things it can do.