Yes and no. I do see your point and thought about that myself, but the input argument is named bVisible, so you set the bVisible = True when you want it visible and set bVisible = False when you don’t want it visible.

“`vba
HideNavPain(True)
“`
should hide the Nav Pain not unhide the Nav Pain.

If the function was named `UnhideNavPain` then the input `True` should hid the Nav Pain.

This control whether or not the Navigation Pane is visible to the user. It does not do anything to the Ribbon. For that you need to use custom ribbon xml and/or database property settings.

Not sure what going on for you. I just tested and even when I call it from within a form, it works fine. That said, I never run it from a form either, I always run it as part of my startup code, the first thing that runs before any forms are launched. My script normally checks my linked table paths, creates persistent connections, applies security, sets database properties, … and hides the navigation pane (actually that is done early on in the sequence).

Simply try to select an object, so:

DoCmd.SelectObject acTable, , True