How to program your own macro feature?

[AdamOnAccess]

I want to build a feature into an access form that works like a macro...

The user clicks a button to trigger the program to start "recording" button events. Then the user goes through a series of common steps on the form that mostly involves hitting additional buttons. While the user hits these buttons, the program is saving events in a table. When the user finishes his work, he presses another button to end the "recording" process.

Now the user can hit a "play" button and the access form will automatically repeat all the events that were recorded.

I understand how to accomplish most of this but I don't know how to write a subroutine that calls another subroutine through a variable. Something like this...

Call VariableThatHoldsNameOfSubroutines

If I try something like this, Access assumes the variable is actually a subroutine and gives me an error.

I hope I explained this well enough that someone understands. Does anyone know how to address this?

[MikeTheBike]

Hi

Of the top of my head I would write a sub that takes an argument to determine which Sub is Run. So, based on you post something like

Call MainSub(VariableThatHoldsNameOfSubroutines)

and Sub MainSub would look like this

Sub MainSub(ByVal SubNumberVariable as Integer)
    Select Case SubNumberVarable
        Case is = 1
            SubOne
        Case is = 2
            SubTwo
        etc......
    End Select
 
End Sub

Is that the sort of thing that would do ?

Note the aurument can be defined as any data type but (IMO) integer/Long are best.


MTB

[AdamOnAccess]

LOL Simple!

I don't know why but I got hung up thinking that I needed something like an "execute" statement. But sure, I could define the buttons with integers, store the integers, and then run them through your select statement.

Sometimes I just can't see the forest through the trees!

Thanks,
Adam

[NeoPa]

Depending on exactly how you plan to use this feature you may find Eval() can work for you.

[FishVal]

• "Application.Run" method could be used.
• "CallByName" method may be particularly useful for you since, I guess, the procedures you want to call reside in forms' modules.