ASPRunner.Net 11.3 Build 44525
What is the best way to troubleshoot slow response on a page using the lookup wizard with Autofill or prevent the user from saving before all the data is returned.
On my page, the user first selects a user from a list page with search this is a static indexed file with 12500 records/rows with 32 columns and responds quickly to the point where the user selects a name, and then Autofill populates 22 fields with data from the look-up table. In SQL SSMS runs all records in under 1 second.
This seems to take 5 to 7 seconds after the user selects a name.
In some cases, on this page, the user may be changing the persons position, this also is a static table, 14,000 records/rows with 32 columns. This lookup will overwrite 8 fields from the first lookup and populate 7 additional fields. In SQL SSMS runs all records in under 1 second.
The second autofill takes up to 45 seconds to populate the fields.
If I turn on global Debug, it returns server error when the select is clicked to invoke the look-up.
Not knowing just how this works behind the scenes my assumption is that when the user selects a name, a query is invoked with a dynamic where clause to return the correct row of data. in both cases using SQL and SSMS the results come back immediately.
So why does it seem to step so slowly between the fields update the values on the page?
Is there a way to speed this up (first choice) then a way to prevent saving the record until the autofill has finished?