@CJ_London - Thank you! I truly appreciate all of the effort.
I wouldn't mind seeing the code - very curious how you keep the subform from moving when the main form is scrolled.
Question - Would putting the nav form in the form footer help, and would Stephan Lebans method help -
https://www.lebans.com/recnavbuttons.htm - That is what I am using now - but I removed the counter since it was redundant.
I think the mainform as a nav form with the target form as a subform is probably an easier way to go
I re-considered this. I appreciate the suggestions by everyone and as you said, I am fairly certain it can work, but there are only a few resolutions where we need to scroll the form to view everything and very little needed info on the right side of the screen. (Translation: If our users have to scroll to the left to go to a new record, we can live with that. There are some static tables on the right side, but nothing that changes that you would want to monitor as you scroll through the records.)
If your solution can be made to work, it does almost all of what I was after. If not, I'll likely modify Leban's code (that I am currently using) to add back in the record counter and maybe a Clear Filter Button, hide the built-in navigation bar, and call it good for now.
I was able to place the bar within the form space itself and does not move on scroll (which is what I think the OP is after)
Correct - demos look good!
however resizing the form means you also need code to keep the control within the form window (i.e. at the bottom as the default nav controls/scrollbar does)
Would putting the nav form in the footer solve this, or would that make it scroll off-screen when you scrolled the form. I like the nav form at the extreme bottom left, so that might be an issue. However, usually we just open the database and leave it open. I can see potential issues if we have the database on an external monitor and disconnect it and move it to a laptop, but if necessary, we could live with "Close and re-open the database if you change monitors" - although obviously not desirable.
And although the nav form is now a child of the main form, you cannot reference it as you would other controls - my guess is you would need to refer to the navform object - but not investigated
Makes sense, but I'm not sure when you would need to do this.
Again, thank you very much!