It is thus easy to see that the problem of providing a highly convenient method of simply adding fields and having them available in grids and mail-merges is intelligently solved using SQL Server views.
This powerful technology however comes at a price. That is because SQL Server will occasionally misinterpret the dependencies between the entity views and return errors when these views are used by the application.
The solution is this form which provides a manual-override and refresh of the views if they become corrupt.
It is generally only necessary to run this function after a field has been added to the database and testing has discovered an inconsistency in one of the grids in the application.
There are other occasions however, where refreshing all of the other SQL Views in the database may be necessary for example following a large data cleansing or import exercise where re-indexing the views may yield better performance. This form therefore provides the ability to refresh these views also.