The time taken from starting the Field Properties dialogue to InfoQube being ready to accept commands is a little over four minutes for one of my IQbases. This seems rather slow and makes incremental development painful.
Reorganising the IQbase makes no appreciable difference.
I attempt to rebuild the same IQbase, and this fails with error-message:
Rebuild failed (Error= Application-defined or object-defined error)
Rebuild failed (Error= Application-defined or object-defined error)
Does anyone have useful suggestions to make?
Comments
<source>SELECT ItemID, ItemID > 0, Left([¯fText].[Value],255) AS DuplicateItem
FROM ¯fText
WHERE (((Left([¯fText].[Value],255)) In (SELECT left([¯fText].Value,255) AS DuplicateItem
FROM ¯fText
WHERE ((([¯fText].FieldID)=1))
GROUP BY [¯fText].Value
HAVING (((Count(*))>1))
)))
ORDER BY Left([¯fText].[Value],255);
</source>
Now since this contains a nested select which reads every item in the IQbase which is repeated for every text item in the IQbase, it is not surprising that its execution is slow! What is a little bit surprising is that every time the Field properties are loaded, and every time when manipulating the Field properties that the cursor lands on or navigates past the DuplicateItem field entry, it seems that the query is re-executed – presumably to keep the Nb Items column in the Field properties display up-to-date?
For item inheritance, row and column equations, there is a button you can press which sets the functionality on or off. However, there is no such button when the field data is defined in the options clause.
Therefore, two enhancement suggestions:
1. Reconsider how often to calculate the Nb Items column? E.g., when explicitly clicked, and not just because the cursor travels past?
2. Perhaps have an On/off button for options code?
Obviously low priority. My workaround is simply to remove that code for the time being; when on rare occasions I need to look for duplicate items, I can put the code back in again.