Search results

I have received MDB's that I need to *un-brick* because it would no longer open in the new version of Access, so, from experience. 99% of the time it's because of a Reference issue or an ActiveX that was used. Not sure about the millions but I have gotten my fair share. You lose nothing by...

It's not change you should be worried about it's that one day you may not be able to open your database.

Well, not sure what you are even doing. Both of these take up the entire screen so how can it query a Form not open? If you are clipping back and forth then once you enter the Container No the record may not be committed (save) to get the value for it to be re-queried. May you can help us out...

Hmm, if you are modifying this database then if other person has to use it it might be a problem. Anything you do in the latest version may not be available in 2003. I'd be very careful.

Oh okay. Perhaps you could start with posting your Relationships diagram.

Yes, requery itself and since you are doing so you cannot put the Form name there. You need to put exactly what I put in the On_Click event. If that works then it's probably not doing from the Main Form because data not saved yet. If that is not working please post the Row Source of the combo...

Hmm, try putting... Me.cboContainerNo.Reuery in the On_Click event of cboContainerNo.

Hmm, can you post a screenshot of the Properties window? Oh, and is Transparent set to *No*?

<---from Ohio Welcome to the Forum!

Well, not usual to have that many combo boxes dependent on the main Form. So, I've never tried that many requeries. All I can say is try it.

Ouch, that is going to painful for some as not everything moves over nicely.

Hmm, just a side note, 32 bit Access is not *legacy*, it is, in fact, recommended by Microsoft. So why would you migrate your applications to 64 bit?

Hmm, so I added a... Me.ServiceID.Requery ...to the On_Current event of the Subform and it appears to do what you want. That said, I would use tables to hold combo box values instead of Value Lists. If you ever need to make a change it's easier to add to a table then to keep going into deign...

Welcome to the Forum! Perhaps this will help... https://www.access-diva.com/vba20.html

Welcome to the Forum!

Welcome to the Forum!

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.