Get value of Link Master Field

[Micron]

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.

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.

[Uncle Gizmo]

Originally Posted by Micron

your prior statements about "abusing" OpenArgs or it being less clear or somehow not being able to separate the values.

I stand by that. I never did like trying to cram loads of variables through in an OpenArgs string, it's just not right. A very clever workaround though ...

Sent from my Pixel 3a using Tapatalk

[Uncle Gizmo]

Originally Posted by Micron

OK, I watched the vid. I get what you're doing but I would use other methods such as OpenArgs to pass the value to the control, or just make mTest public and code as below. The behaviour that you say is unexpected may be to some at first, but it is exactly what I'd expect and it makes perfect sense.

The property value isn't assigned until execution returns to form1 where you have .prpTest = "TEST". It is too late now because the form2 events that attempt to set the control value are not going to run again after you define what they should have used as a value. To me, this is just how code executes when control passes from one form or procedure to another.

Obviously you're not going to change the way you do things just because I don't see an issue. After all, your fSetup is only 3 lines long.
Here's how if the property declaration was Public (not going to bother with OpenArgs):

DoCmd.OpenForm "frm2"
Forms!frm2.mTest = "TEST"
With Forms!frm2
    .txtShowResult = .prpTest
End With

I'm not happy with the idea of making the custom property variable public. In any event it's not necessary because just a slight change to your example:-

DoCmd.OpenForm "frm2"
Forms!frm2.prpTest = "TEST"
With Forms!frm2
    .txtShowResult = .prpTest
End With

And it works fine...

[MajP]

OpenArgs and custom properties is an apples and oranges discussion. OpenArgs is a workaround for a limitation in Access that custom properties cannot address. The only time OpenArgs is needed (and required) is if you open a form in ACDIALOG. Because code execution stops in the calling form there is no way to pass anything to the called form. OpenArgs works like a parameterized constructor where you can pass in a value at instantiation. If you do not open the form ACDIALOG then custom properties or other solutions are available. I agree, if you do not open ACDIALOG then overusing OpenArgs is not a good approach.
Working in something more modern like VB.NET is much simpler because you can set properties of the form before opening the form. So for example you can set the value of a textbox before even opening the form in a dialog mode. The purpose ofOpenArgs is a workaround for the limitation in Access or not being able to set these properties before opening in a modal/dialog mode where code execution is given to the called form.