Performance Checking

There are a number of areas in Data Editor where there is a potential for slow performance, depending on the number of records in certain database tables and on specified filter criteria. For example, if the Item_Prod table contains many records and no filter criteria are entered in the Item Production Filter dialog box, clicking Apply on the filter dialog box could cause a long delay while the records are retrieved. Similarly, if the Item_Prod table contains many records with different operations starting with the letter A, and the filter criteria A% is entered in the Operation ID field of the filter dialog box, a significant delay could occur between clicking the lookup button for the Operation ID field and when the lookup dialog box appears.

To limit such potential performance problems, every place where filter criteria can be entered to limit a database result set, Data Editor will first check the size of the result set to ensure that it is not too large (a system parameter determines what that size is; for example, it might be set to 5000 records). If the size of the result set exceeds the defined maximum size, a message appears, allowing you to either proceed or to cancel the request and specify different filter criteria.