Search results

Welcome to the Forum!

Ah, I'm now seeing the *bigger* picture. So in creating a Module you are hoping to use one line to call the code for the buttons? Because no matter what each button is going to need something. Nope, let me restate that... you could just use an Embedded Macro for each button and then the code...

My bad, I thought those were tabs but I see the tabs now. Hmm, then I am still missing something... So you have now selected your Building ID Then you open bldgform, I am assuming from the Main Menu, which will show the name of the building. From the bldgform I can open the reports which are...

Nothing is coming to mind right off the bat. Especially because ANYTHING could change. Is there anything that remains the same? I mean writing a Module to change anything would be just as bad as changing all the Forms individually.

You mean like change the report it was printing?

Hmm, I would store image, location of command button in a table but okay. What could be common? The placement? The image? And now I'm not getting what the Module would be used for? If you are just *moving* the command button the code goes with it since it's on the one Form. If it's on a...

And a screen shot (or maybe a couple) might help because no way there is not an easier quicker way to get this done.

So, here's me trying to figure out what you are saying here... Are you just changing the background picture but the buttons stay the same? No need for different Forms. Just apply what Micron made reference to, have a table that stores the path to the image and when you look up the Building...

Perhaps you should paste the code you have now.

You can what @Isaac suggested but if it's on the Form not sure why you need to declare it. It should only pull for the referenced control. So, once you select the Building you can just pick any report you want to print, the code does not care that you are clicking a different command button.

You can just put the DoCmd.OpenReport.... lines under one Command Button., no need to separate them since you want them to all open at once.

Hmm, not really suited for a Module if each report has different parameters and names. I mean you could do it but seems like more work than it is worth. Each report will already opens filtered. You just need to copy the code and change Report Name and Where statement. Or am I misunderstanding?

I was not disagreeing with you, sorry if it came off like that. Was just pointed out that not really necessary unless that control is not on the Form. (Always more than one way to skin a cat. (My apologies to the cat lovers. 🙃 ))

There is no need to declare a control which is already on your Form, unless it is NOT a control on your Form and a Public Variable.

My bad, get rid of the acNormal at the end... DoCmd.OpenReport "rptElevators", acViewReport, "", "[BldgAbb_ID]='" & Me.BldgAbb_ID & "'"

Hmm, try... DoCmd.OpenReport "rptElevators", acViewReport, "", "[BldgAbb_ID]='" & Me.BldgAbb_ID & "'", acNormal

Welcome to the Forum!

Hmm, I use something simliar https://www.access-diva.com/d11.html But I also use MZ Tools because it allows me to use shortcuts to quickly insert code I use constantly, less typing.

Hmm, so using look-up tables as the Row Source for Combo Boxes and Autonumber as the Primary Key I append 0 (zero) as the first entry. This allows the User to select *nothing* from the Combo Box and allows me to *tell* the Filter what to do, in my case show all.

Little known fact, when the boll weevil threatened the the cotton crop Booker developed a rotation of plantings, corn and peanuts to save the *industry*. And for his good works they built a statue to the boll weevil. Hmm, I am starting to think building *statues* to the losers has somehow...