Column headings remaining visible

[Micron]

June is so far into this that I hesitate to go over the same ground, and June is more capable than me for sure. But I do have a suggestion to shorten code that you might be able to make use of. Instead of 50-ish lines that set properties such as .visible, consider something like

dim ctl as control
For each ctl in me.controls
    if ctl.type='acControlTypeGoesHere' AND ctl.tag="yourTag" then
       ctl.visible = true or false as you wish
    end if
next ctl

If you want to apply this to more than one type, it's probably easier to trap the error that is generated when you try to set a property on a control which does not have that property. In the error handler, you RESUME for that error number. I don't remember the number...

[June7]

Micron, if you can download the db and get the form to open without error, please continue.

Whether or not the shorter code will perform faster I can't say for sure. Might depend on how many controls must be cycled through. Directly setting visibility property of a few controls might be faster than cycling through hundreds.

[bradp1979]

Just now figured it out. The lines of code naming Me.lbl____.Visible = False, etc. was in the VBA twice. I just had to find the second one, and add Me.lblExpected.Visible = False and Me.lblParked.Visible = False to vendor 44 and 48, and Me.lblExpected.Visible = True and Me.lblParked.Visible = True after the Else statement in both places. Now it works.

[Micron]

Interesting, because my point was not about speed - it was about less typing, easier to read/follow and less chance for screw-ups. Easy enough to modify object tags too. Glad you got it solved!

[June7]

I know you intended to save on typing but typing is done once, the procedure must run repeatedly. Shouldn't performance be a consideration in coding?

[Micron]

Of course performance is always a consideration and I did not mean to imply otherwise. Had I known there were "hundreds" of controls on his form that were of the textbox type, I still would advocate this method for where it makes sense.

I do not know what the limit would be before you would notice a performance hit, but I can tell you that you would need to get the system time in milliseconds before and after each routine to notice a much of a difference with 100 or so controls. Even when I have stepped over this routine in the vbe on a form with over 100 controls, the processing time is around a second or so. Like many repeatable tasks, it can also be called as a function in a standard module where you pass the control type and tag text as values, thus reusing over many projects. That would be worth 1 or 2 seconds of processing time in my opinion. In this case, it might even have prevented the issue.

With all due respect, I reiterate: my point was not about code execution speed, it was about passing on a method which has certain advantages that one could take or leave depending on their situation, because I seek to inform as well as learn here.

[June7]

I don't know if form has hundreds of controls nor whether the performance would suffer, just trying to inform OP of things to consider. I do I have some complex form/subform arrangements that are already slow enough so I use the 'long' code.