Hi
My application is not deployed over a network yet. I do my best to anticipate performance concerns in the mean time. But i have some questions, given that I have
never deployed an app over the network.
Let me make some assumptions for you:
SQL server or regular Access backend
Assume "average" or above average network speeds
small business environment
Now to my question specifically, a common interface i use in my forms (unbound) is a listbox selection to dynamically allow the user to browse data. See the image attached.
In your experience, with the interface below, would this be a somewhat laggy experience for the user? Would it take a discernible amount of time to load the contact info in the textboxes based on the
user's selection? If they were browsing through the list quite aggressively, would this be uncomfortable?
This would of course be loaded using DAO recordsets with VBA and querying the data directly from the backend as the user changes selection. Not many fields to return, maybe 10 fields of short text data type in most cases.
My anticipation is that this will be somewhat laggy over a network. Maybe this is not true. But i have been remedying this solution by loading a TEMP table when the master record is loaded. The user reads/writes to the temp table
until the user finally saves the master record and writes the temp table changes to the backend before closing. Is this a waste of time?
Perhaps I can provide a better understanding with a sample. I will await feedback.
Thanks for your help!