Access and Azure SQL Database

JoseAntonio110 This is a very well known problem, unfortunately. 

Depending on how you designed the Access forms, you MIGHT be able to improve performance by adopting a few practices.

One, if you are loading the forms in the traditional "Access way", you are binding the form to a table and applying filters to it to select or navigate to specific records. If that is how this was designed with Access tables, it works well, but when you are pulling records from a remote SQL Server, i.e. from Azure, it is really inefficient, and therefore, slow to do it that way. Instead, all forms should be designed with single record queries. Apply criteria that select and return one record and a time and requery that one-record recordset in order to navigate to other records.

A second factor that can make a big difference is having a lot of combo or list boxes on the form. Each of those has its own recordset to pull down from the SQL Azure database, and that also slows things considerably. 

The same is true of subforms. Each subform, in turn, also has its own recordset, and again, that adds to load times.

In short, interface design for Access relational database applications linked to remote databases, including SQL Azure, depends on pulling the least possible traffic across the wire from that remote database. 

Focus on that first.

Other things that can sometimes help might include using passthru queries whereever possible for rowsources in combo and list boxes. Although they are not significantly better in all cases, Passthrus do tend to perform better.