Forum Discussion
Improve performance Access frontend with Azure backend
> however the form is not updateable any more.
That is probably because you used a PT query. They are never updatable. Rather you would select 1 row from the linked table or a query based on a linked table.
> the performance often leaves something to be desired
> customer will not be happy if the entire application has to be rebuilt all over again
It appears you're going about it the wrong way: it seems YOU decided performance was not adequate, and you THINK customer will not be happy.
That is for them to decide. Presumably they decided on Azure hosting, and they have to understand that comes with consequences. They will have to decide how much time and money they want to invest in making it faster, and what parts of the app should be focused on.
If you search online you should find plenty of discussion of this topic.
One technique I can recommend is local caching of quasi-static tables such as Statuses, States table, and others.
- Thank you for your help Tom, data caching is definitely something I will dive into.
- Two other things that can improve performance are NOT to bind forms and reports directly to tables, and making sure that all tables are appropriately indexed.
Part of the performance problem with a remote back end like Azure is that calls to the database for data go out over the internet. Pulling large datasets across that connection is inefficient and slow. Therefore, you want to minimize the number and size of those recordsets. That's where local caching shines. Also, if you want to edit a single record, use a form bound to a query with a filter that returns only that one record. Obviously, efficient indexing can make tasks like filtering and sorting faster. That is probably more of an art to get it right, but it should be included in your preparations.
