I have quiet a large database, which I want to filter by an embedded view. This worked for many years without problems…
Now we are switching from R5.11 to Release 6.5.2 and I have made some changes to the functions, which slowed down the response time drastically.
In the past:
I have started a form with an embedded view. In the post open event of the form I save d the document when it was new. Afterwards opening it again, displayed the embedded view nearly at once. In addition the document was moved to hidden folder for deleting temp docs. This is done by a scheduled agent.
Now:
I have changed the form with the embedded view, in order to reduce the overhead by the temp docs… (The field SaveOptions is set to “0”). I never save this document now. There is a computed field over which I select the category in the embedded view. This takes at a minimum 4 minutes to display the contents belonging to the selection. In the meantime I only see a grey box with the view alias name.
Does anyone have an idea why this takes so long?
Subject: Embedded View on large database very slow
Hi!
I am experiencing the same problem on R7.0.3
There are about 40 views in the database, and 9000 documents, the embedded view’s selection uses a form of which there are about 1000 documents.
The embedded view’s “view selection” and “single category” properties refer to editable text fields located above the view.
Problem: The content of the embbeded view is only shown after a delay of ca. 4 minutes.
For testing purposes I put a duplicate of the embedded view below the first, but “hardcoded” the name of the view selection and single category, instead of field names.
The content of that second embedded view within the same document is shown instantly, while the first view’s content appears automatically only after waiting 4 minutes.
Any ideas what’s going wrong here?
Subject: Embedded View on large database very slow
Hi Holger,
we have a resembling case:
Large Database with Forms including very large embedded views.
Can you exclude it is not the view which makes it slow?
For Interest: How do you change the category that is the computed field without saving your form?
(We solved this using a profile document so we have a setting for every user)
Hope this will help
H.Mueller
Subject: RE: Embedded View on large database very slow
I do not think it is the view, because when I make it the “old” way it works well.
When we start the form with the embedded view. it is not necessary to change the category. When we change the category, we open a new form with fields which have the category included. (During the compose, I set the fields with the needed values from the above document by lotus script.)
The setting for every user does not solve my problem.
We use it for filtering the correspondence for a selected customer. We have several thousand different customers…
Thanks