I have employed this method in one of my screens, to enable the user to quickly navigate through records:

Example of using a layout script triggers

Many new users to FileMaker come from a spreadsheet background. As a developer, you can give them a more spreadsheet-like experience in table view by using the onLayoutKeystroke script trigger. It will allow them to use the arrow keys to navigate fields and records like they would cells in a spread sheet.

Step 1. Create the following script, and name it "Navigating table view."

If [Code (Get ( TriggerKeystroke )) = 29 ]

Go to Record/Request/Page[ Previous ]

Else If [ Code (Get ( TriggerKeystroke )) = 31 ]

Go to Record/Request/Page [ Next ]

Else If [ Code (Get ( TriggerKeystroke )) = 30 ]

Go to Next Field

Else If [ Code (Get ( TriggerKeystroke )) = 28 ]

Go to Previous Field

End If

Step 2. Navigate to a layout that's viewed in table view.

Step 3. Enter Layout mode.

Step 4. Navigate to Layouts > Layout Setup… and then click the "Script Triggers" tab.

Step 5. Check the "OnLayoutKeystroke" event. Select the "Navigating table view" script we just created. Hit ok when finished.

Step 6. Enter browse mode, use the arrow keys to navigate the fields and records.

Result: The user will now be able to use the arrow keys to navigate a table in FileMaker just like they would in excel.

Although it works just fine, the problem is that in a list view with many records (exceeding the screen) if you press continuously the down arrow, at some point the current record disappears and you have to go back-and-forth one time to make it appear inside the window.

Can anyone figure out why this happens?

New discovery about the problem:

It only happens when no field is selected.

The specific window serves as a quick selection popup window with only a search field enter-able (spotlight-like)in the header.

If this field is not active, then moving along the records (if too many are shown) sets the current record outside the boundaries of the shown records.

Anyone seen that again?

I can't quite visualize what it is you are observing. Would you be able to attach a screenshot or maybe even a sample file?