I have a form with 89 fields, some of which are note fields with very long notes. When I’m looking for a specific field in the default view, scrolling up and down through 89 fields is pretty inefficient, and I often scroll past the field I’m looking for without realizing it. (It would be easier to keep my bearings if there were two or more levels of section headings – similar to h1 and h2 in html – but there’s only one. As a workaround, I use a different color label to indicate “h2” section headings, but since it’s still the same font size as the other labels, it becomes a text soup.)

I intuitively expected that when I clicked on a field in the table view, I would jump to that field in the layout view, but no such luck. Would it be possible to make it work that way in the next release or at least a future release? My database will eventually have over 200 records, and all that scrolling is taking its toll.

Thanks for the feature request. Interesting idea. I wonder if there would be situations where this would really annoy people. Such that they click on a cell in a record but they really want to edit the first field, but it jumped to the 50th field instead. So they would have to make sure they always click only on the first cell in the row they were interested in.
Perhaps “jump to field” could be a preference setting. Or perhaps shift-clicking on a field would leave the form in its current position but regular clicking would “jump to field.”