Next New Issue - Manipulating a standalone Label to change the text

[ScubaBart]

I have a couple forms that depending on the mode that I open them (whether to edit and existing record or add a new record), I want to have different Titles and Notes or instructions.



I have tried so many different options including some in VBA and nothing is working.

I have tried the box as both a standalone Label and an Unbound Text Box.

Tried changing the Caption and the Value. Have used every imaginable variation of syntax.

The typical error is that the referenced control is not found. Getting this in both Macro and VBA attempts.

Surely it shouldn't be that hard to simply change the words in a Label or Text Box.


What am I missing ???

[orange]

Show some code --highlight the issue.

[Welshgasman]

No it is not.
Label - Me.LabelName.Caption = "whatever"
Textbox - Me.TextBoxName = "whatever"

[Micron]

To add to those comments, if the same form is being opened in different modes, then pass that mode value to the OpenArgs property of the opening form. Based on that, set the values of labels/controls.

[ano]

are u sure that form is already open? did u put ur text depending on condition in on load event?

[ScubaBart]

are u sure that form is already open? did u put ur text depending on condition in on load event?

Yes, here is the macro I am currently playing with and the form opens before the error pops up.



To all other replies, I have not had a chance yet to apply the ideas as they involve VBA and it will take me a little time to sit down and absorb the info. I am not well versed in VBA so it takes me a lot longer to create and troubleshoot that version of control.

Will be working on it soon though and advise of progress as it is made.

[ScubaBart]

No it is not.
Label - Me.LabelName.Caption = "whatever"
Textbox - Me.TextBoxName = "whatever"

This is what I am trying



This is what I get when I try to Compile



The form has the two Standalone Labels with just the names of the labels as filler text



So, what am I still doing wrong ?

[Welshgasman]

Me refers to the form you are running the code in.
You would be better off setting it in the detsination form using OpenArgs.

Otherwise you need something like

Forms!FormName!LabelName.Caption = "whatever"

[ScubaBart]

Me refers to the form you are running the code in.
You would be better off setting it in the detsination form using OpenArgs.

Otherwise you need something like

Forms!FormName!LabelName.Caption = "whatever"

The example you provided works so I will use that.

I am not familiar with OpenArgs. I may have to learn at some point but if I have something that works, I am going to use it.

Is it safe to expect to be able to address all parameters in the same way as changing this caption ?

[Welshgasman]

As long as they exist.

[Micron]

You would be better off setting it in the detsination form using OpenArgs

Thanks for seconding that
According to how one interprets ms documentation it should be possible via macro but I'm not seeing how. I suspect TempVars is available though so that might be an alternative.

[Welshgasman]

Yes, you can set Tempvars from within macros.

[ano]

using docmd create new instance outside ur form, so ur caption need in other form on load

[davegri]

In the macros, the Value requires an =; Value ="Apiary Detail Edit"

However that presents another problem discussed in google searches. The macro will not look at the form just loaded, it tries to apply the action to the form that executed the macro action.
So the calling form needs to set a value for the called form to look at so that the called form can issue the macro action. Tempvars would work.

[ScubaBart]

In the macros, the Value requires an =; Value ="Apiary Detail Edit"

However that presents another problem discussed in google searches. The macro will not look at the form just loaded, it tries to apply the action to the form that executed the macro action.
So the calling form needs to set a value for the called form to look at so that the called form can issue the macro action. Tempvars would work.

If that's the case with macros, that could explain several actions I'm having issues with.

Have never worked with TempVars though so I am doing what someone above suggested and made a copy of the entire databse and turned all the macros into VBA for reference so I could start converting anything that was causing problems into code. So far, so good but I'm sure something will still cause me a problem.