We have a problem that two users are experiencing, but we cannot replicate. A window showing a date entry datawindow of transactions calls ScrollToRow(dw.RowCount()) to put the cursor on the last row. That always works for us (and we believe most users) but for two users, the 1st row is displayed instead of the last one. But if they press Tab, it moves to the 2nd field in the last row (scrolling to display it).
So that's why I say it's behaving as if only SetRow was called.
We have see a PBDEBUG output and only ScrollToRow is ever called, never SetRow.
Any bright ideas?