>
>Hi Cetin,
>
>You'd not reach the maximum number of datasessions which I believe if 64k. But that is not the point. In our case we have a patient file form which progressively would load folders with in total hundreds of comboboxes on there. This would mean hundreds of cursor and hundreds of potential collisions of cursor names, especially when you reuse classes (like dropdowns for physicians).
>
>And yes, we use private datasessions (see my datacache argument above) everywhere where applicable, Its just that some of our forms contain many, many comboboxes
>
>I have a hard time to see the advantages of cursor populated comboboxes: I do not want to do SQL on it, nor do I want to locate a record in there. The value property will do everything I need
>Listboxes are somewhat a different case as you might want to use it to navigate with it, but then you are using the cursor for more than just population of listboxes anyways
>..
>Btw, do you know what might happen in your case when having many cursors when you issue SYS(1104) with a virusscanner active? It took me many weeks to find the cause of massive delays at a clients site to come to that diagnosis.
>
>So, no I do not advise anyone to use cursors to populate comboxboxes. Do it clean and use array properties on comboboxes themselves.
>
>
>Walter,

Then what is the point? As I said to Dragan, you can simply name your cursors after the combos they are bound to. If you don't like that you can put sys(2015) into tag value and use it.
I find it weird, to have hundreds of combos and find hundreds of cursors a lot.

Value property cannot do everything one needs. It has the capability of holding a single value. However with cursors you would have access to any field you have included.

So I advise everyone to use cursors to populate combo\listboxes. I do it clean and use cursors.