This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
One really need to look at your application to see what the issues are that causes bad performance. But a start is the number of views, the number of documents in those views (as well as the selection criteria for those views), view index settings, etc.
You also say that you have multiple @DbLookup in yoour form. You should either consolidate them into one (or at least very few) lookups, for example if they pull from the same place (e.g. first name, last name, address, city, email, etc), or rethink the approach of how the document is updated.
You may also want to consider using Lotusscript to load data into the document in the QueryOpen event, depending on what you are doing it may be faster.
Other things that could cause slow code is the dreaded GetNthDocument (never use!), or that you use doc.GetItemValue() to check each document as you loop through a view or a document collection based on a view.
You should consider creatinga NotesViewEntryCollection and loop through the view entries there, using the ColumnValues property to read values much faster than you would using GetItemValues...
Performance
Return to top
. . Performance (~Dan Kikiterobu... 14.Oct.14) 
