shortcut for Repetitive button coding?

[epardo87]

Hello there,

I have a point of sale form to be used on touchscreen devices, for which I have a button made for each product. I have 105 buttons split into tabs of about 10 buttons per tab according to the kind of product. the thing is, I've already created a custom function that contains the formula for each button, but I'm having all this repetitive coding that I believe there might be a way to do this with a loop or something perhaps, I'm no programmer and it's been years since the last time I used access but I've been finding my way to write most of this form with VBA.
the custom function is called "Buttons" and the only thing that change is the product's part number in the name and the code... is there something you would suggest?

thanks for your time in advance

Private Sub PN2001Btn_Click()
    Buttons 2001
End Sub
Private Sub PN2003Btn_Click()
    Buttons 2003
End Sub
Private Sub PN2004Btn_Click()
    Buttons 2004
End Sub
Private Sub PN2005Btn_Click()
    Buttons 2005
End Sub

...

Private Sub PN****Btn_Click()
    Buttons ****
End Sub

[Micron]

Not sure what you're after.
Perhaps it is something like this: you can create a function in a standard module that accepts a parameter for the Screen.ActiveControl.somePropertyHere, where the last part is the name, tag, caption or other useful property of the button that was clicked. Then in design view you can select a whole whack of buttons (what is a whack anyway?) and set the On Click event property to the name of that function. When clicked, those buttons will run said function. In that function you could use a Select Case block to determine what to do. However, you will have 105 Case statements in that block - something that I've never done to that extent. Each one of those case statements would do something different if need be. I say that because I don't know what those 105 calls to "Button" do.

There are probably other solutions; one perhaps being to use WithEvents. However, I must confess to never having used that method, and FWIK it would require you to declare 105 variables (one for each button) but don't quote me on that. Perhaps someone knows how to write a class for all command buttons that can distinguish between the 105 of concern and ignore ones that do things like open forms, but that's not me.

[June7]

Maybe with some fancy custom class coding.

Otherwise, what you have is about as compact as you can get.

[Minty]

I'm a little wary of the need for a button per part number as a structure?
What happens when product 106 arrives? You need to add another button and code to accommodate it?

This sounds like a data structure design issue rather than a problem with repetitive buttons, unless I'm missing something obvious?

The obtuse answer is that each button would be in a repeated subform, and that the product code was allocated in code on form opening?
The code could then be based on the product code not the button number?

[moke123]

This class will handle any number of buttons. This example has 42 buttons with no code behind them.

[moke123]

Another version which is more like a point of sale

[Bulzie]

Instead of all the buttons, could you just have a combo box of Part numbers and code behind it to do what you need for the specific Part?