Setting Up A Macro to run VBA code

[Lou_Reed]

Okay, the question that I have to ask is this.



I have been working with examples that are subforms and associated VBA code. Now I must change the Sub updateButtons VBA to reflect what is on that subform. So to do that I must see the subform and the only way to do that is to open up its main or parent form. To open up its main or parent form is to know from the subform what its main or parent form is.

That is my question. If I know the subform's names, how do I find the main or parent for, to open it and see the subform


If I do not know this I certainly cannot modify the controls in the Sub updateButton subprogram to reflect what i on the subform.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[Lou_Reed]

In looking for controls, I feel like you're going about it the wrong way. You have the code on frmPersonnel. What do you want it to do? What controls on that form do you want to enable? Decide that, find their names and adjust the code.

Sub updateButtons

When you say adjust the code you mean adjust the code in Sub updateButtons()?

Regarding calling the function, it doesn't have any arguments, so there shouldn't be anything after the function name. As you have it in your code:

but in some lines of my code there are arguments, for example :

DoCmd.RunMacro "FormHeading", , ""

which I wrote like this

FormHeading ", , "

the compiler did not complain so i think it is at least syntactically correct. Is it functionally correct?

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed


which I wrote like this

[pbaldy]

but in some lines of my code there are arguments, for example :

DoCmd.RunMacro "FormHeading", , ""

which I wrote like this

FormHeading ", , "

the compiler did not complain so i think it is at least syntactically correct. Is it functionally correct?

Apples and oranges. The first runs a macro, the second runs a function. The RunMacro action has arguments, your function does not. You might not get a compile error, but I'd suspect a runtime error since the function isn't expecting an argument.