Access Report and Form Tips

Avoid restricting records or performing calculations within the form or report.

Place record restrictions and complex calculations at the query level. Use a filter only if absolutely necessary and only at the query level.

Place static look-up tables in the front-end database when you have that option. Splitting the database into a front-end and a back-end improves performance by reducing the load on the network. Additionally, it allocates memory more conservatively since the static tables are accessed at the front-end.

Use list boxes and combo boxes to enhance the user interface, but use stored queries for any that rely on a long table or on a query involving joins.

Avoid combo boxes with thousands of entries. Such a large amount of data hurts performance when the form opens and when the combo box displays the list of values.

Use a separate text field for value input paired with the combo box when it has a large number of entries. Use the input text field to restrict the list of values returned after update event. To do this assign the source of the combo box programmatically by using the first few characters typed into the paired text box.

Avoid using a switchboard menu or other menu system where no forms are selected until the user takes action. Such menu systems cause the front-end database to attempt deletion of the .laccdb file on the server several times before it fails. This avoidable activity degrades performance of the linked database.

Use a menu with a small form or a recordset that is open all the time. This approach improves performance by preventing the front-end from continually checking on the .laccdb file.

If you haven't time to implement these tips or if the development resources available to you are unable to make progress, please contact us.

Tips on Compacting Microsoft Access Databases >

By Admin at 1 Nov 2016, 16:50 PM



Post a comment

Please correct the following: