Andy,
Hello. I have thought on it... I guess I don't see any advantage to using 'LET' if you can't execute code the way I desire.
For instance....
CLASS:
SUB:
So, if I wanted to LET Online Property to TRUE (i.e. do some meaningful work in a database or sheet) then its reasonable to assume, my only option here is to design a method...
Example:
CLASS:
OK So now when I write my procedure in my module to use this class, it will look as such...
SUB:
An example of my problem is a Textbox object. You can get the value like this...
You can LET the value like this....
However, maybe I am ignorant, but I would bet when you LET that value, behind the scenes there is much more code being executed (find the specific textbox object, enter the value, etc)
(i don't know how MS writes their software nor do I have any knowledge of "true" program objects) But I am just making the point that there has
to be a valid case for when a property is LET with a value, code executes. And i'm sure thats possible, I just don't know how right now lol.
But going back to my philosophy and way I am using this class, I realize that it boils down to....
-Properties hold variables to use later
-Methods use those properties
So, I am all over the place lol. Just trying to make practical sense of it all and leverage these tools.
Thanks, welcome your comments and criticism.
Bookmarks