Optimizing Access Interfaces for Editing w/Remote SQL Server/SQL Azure

In this video, I concentrate on ensuring that users load the minimum number of records for editing. The optimal number of records in an editing form would be one--the one record currently being edited. (This is the corrected version.)
The goal of interface optimization is to retrieve the minimum number of records possible from the remote database to complete the current task. There are many ways to optimize Access with SQL Server, including things like properly indexing tables and leveraging views and stored procedures to move the more complex calculations onto the server.
I demonstrate one approach to interface design that attempts to minimize the amount of data moving back and forth from the server.
To learn more about the mobile interface for the Lander Trail Foundations Library, check out my PowerApps 4 Access Devs Playlist. • PowerApps 4 Access Devs
Limiting selections available to the user in the interface.
• Optimizing Access Inte...