Wow 7 years and nobody thought to requery the recordset instead of the form...
Me.RecordSet.requery.
Hell you can even pick the form you want to requery the subsequent recordset on... because it turns out refreshing the data is what you need to be doing not the form because of course it is...
When you requery the form you are going to.. Spoilers here... refresh the form.
When you requery the Dataset you refresh the dataset within the form but not the form itself so the scroll bar does not move but the data updates.
Forms!frm_Name.Form.Recordset.requery
The reason Microsoft didn't create a solution to the forms requery issue is because there isn't a problem with it, there is a problem with you doing things bassakwards.
Wait... someone created a whole set of scroll bar logging positions to solve this... what muppetry is this!? It's like building a bicycle from scratch every time you to go to the shops when you own a car but then still driving to work.
Hold up, you use RecordSet in your form position logging algorithms!!! Really... nobody stopped to think oh yeah RecordSet exists... requery the RecordSet.
So it's like you built the bycycle to go to the shops while still driving to work and then lubed the bicycle chain with the oil from your car.
Straight up lunacy. Just stop and think about what you are doing before going down a rabbit hole for 7 years...
I am sorry I didn't happen across this sooner I signed up just to help people out who happen across this issue and let this be a lesson to you coders out there rabbit holes are bad mmmkay.
Always trouble shoot what are you doing, then stop and think ok what am I really doing...
Is there a more efficient way before creating a scroll bar logging algorithm and relative position index for NO REASON...