Quote:
Originally Posted by Uncle Gizmo
So why not the values of Custom Properties?
|
I stated why not (The property value isn't assigned until execution returns to form1...) which simply means your attempt is late, but I guess SomeSmurf stated it more clearly. However, OpenArgs IS a property of a form. Its value is passed to the opening form without having to write a custom property for the same purpose.
Quote:
I suspect it's deliberate , (or possibly a mistake!) In one way it makes a lot of sense, if you are using custom properties m, then you are taking control of the situation, and adding your own function to apply the custom properties is just another step up in this control you are exercising. In other words, you're not relying on the built-in functionality of the form ...
Sent from my Pixel 3a using Tapatalk
|
Sorry, I don't buy into that at all, or your prior statements about "abusing" OpenArgs or it being less clear or somehow not being able to separate the values. We just have different opinions on the matter, I guess.