Ever since I installed Word 2019, I cannot get PgDn and PgUp to place the cursor at the top of the next **screen** of text, in Draft mode, as it did in Word 2010. It either goes to the top of the next **page** (after the page break), or to the same line it was on in the previous screen (if it was on the tenth line of the previous screen and I hit PgDn, the screen advances and the cursor is on the tenth line of the next screen).

I had tried macro-ing it, but that didn't work either.

The keystrokes I recorded for the macro (PgDn to advance to next screen, Ctrl+Alt+PgUp to move cursor to top of screen) produce the code below. (They work fine if I do them manually!) I've been doing it manually for now, but four keystrokes and two hands for what used to take one keystroke and one finger is quite annoying!

The macro code that doesn't work is this:

Selection.MoveDown Unit:=wdScreen, Count:=1
Selection.HomeKey Unit:=wdWindow

It returns an error of "Run-time error '4120': Bad parameter". In the VBA editor, the second line is highlighted.
I tried adding ", Count:=1" to the second line and this returned "Compile error: Named argument not found."
Changing "Window" to "Screen" also gave me the "bad parameter" error. Adding the "count" gives the compile error again.

The command assigned to Ctrl+Alt+PgUp (which I used to return to the top of the screen and generate that second line of code) is StartOfWindow. I haven't been able to find a way to translate that into VBA code that works.

I found this page, which suggested that "WordBasic.StartOfWindow" should work. It does not; cursor in middle of screen again.
https://www.office-forums.com/…/runn...ommands.1865…/

This page seems to back that one up (Search for "startofwindow"): http://www.exelana.com/techie/vba/MacrosReport.pdf

----------------------------------------------------------------------------



It looks to me that in Word 2019, they changed the native way that PgDn and PgUp work. Yes/no?

I have no idea why my macro code won't run. I've consulted with Jack Lyon of Editorium on this, because at first I thought it was an ETKPlus problem, but that appears not to be the case* and he seems to be stumped as well.

*The ETKPlus custom macros for PgUp and PgDn place the cursor at the top of the PAGE, which is useful when you are in Page view, but not in Draft view, which is my preference so I can work a screenful at a time.

Thoughts? I am tearing my hair out.