Forum Discussion
Solved
Improve performance Access frontend with Azure backend
I have the following question. I have migrated a "traditional build" Access frontend application with a SQL server backend to Azure SQL. The linking goes fine, however the performance often leaves...
> 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.
Welcome to the true "performance" of Access+SQL
Simple things...binding the forms/recordsets to tables ...is slow
What you can do...well you need to replace whatever you can with PT (as you did), create some good amount of temp tables for caching, maybe check the performance when you load e.g. comboboxes with in memory arrays and so on.
If nothing does the job then you will need to work on the unbound scenario where the data are INSERTED on demand but the form is unbound and the form is populated only with the minimum amount of required data.
Simple things...binding the forms/recordsets to tables ...is slow
What you can do...well you need to replace whatever you can with PT (as you did), create some good amount of temp tables for caching, maybe check the performance when you load e.g. comboboxes with in memory arrays and so on.
If nothing does the job then you will need to work on the unbound scenario where the data are INSERTED on demand but the form is unbound and the form is populated only with the minimum amount of required data.