Hi All,

I am looking for an alternative to ComponentOne FlexGrid due to issues moving from windows 7 to 10/11 (the combo list dropdown becomes incredibly slow)
Anyway, iGrid was suggested and it looks great so far (I am using the demo)

We use the grid as a order entry system using a stock code. We have around 25,000 lines which the customer can order.
Using FillFromRS it takes about 6 seconds to process the ADO recordset (MSSQL backend) which is not bad at all.
However, the stock items dropdown combo is used in many places in the program, entering an order, stock control, setting special prices, etc.
Each of these is a different form and therefor a different iGrid.

With ComponentOne you an use BuildComboList and assign the output to a public string and then assign it to any combolist as the form is loading.

Is there anyway to do something similar with iGrid?
i.e. store the output of FillFromRS and then assign it to any new iGrid combo when the new form loads?
(or maybe some form of combocopy from a hidden master)

While the 6 second "initialisation" delay is fine on program startup its too long for every form load.

Mike

Thank you for your interest in our product.

As a rule, drop-down lists are used to select from a relatively small number of items. Can you tell us what information is stored in your long drop-down lists and how users find the item they need?

iGrid's combo box cells are built on the native Windows combo box controls. These controls are not optimized for building extra long lists, and this is one of the reasons why we can't speed up list population - be it FillFromRS or an import from a string. Among other reasons, we can mention some internal operations performed by iGrid when creating each element, which are necessary to provide other conveniences, such as automatic item height. Sorry, but I think we can't help with optimizing this task in the current version of iGrid.