>Hello,
>
>In FPW2.6 we used to make all our picklists with a browse and used JKey for the incremental search.
>We used radiobuttons to change the order of the list from descending to ascending and change the order and number of the fields on the screen (and thus the JKey key) also with radiobuttons, this all very fast and even when the lists was very large no delay could be seen and the list changed quickly on the screen.
>
>Now in VFP we use the Listbox to make a picklist. We do not need JKey anymore because incremental search is built in already. We still can change the order from descending to ascending and order and number of fields on the screen but with larger lists it takes time for the screen to rebuilt (requery).
>This can be a problem with some of our large picklists and we ask ourselves:
>
>Should we go back to use the Browse (grid in VFP) and find a way to replace JKey or should we stay with the listbox and avoid using large picklists ? We think ourselves that we should try to make all our applications easy to upgrade to a client/server situation and we think browse is not very client/server so we tend to stay with the listbox only. But what with the large picklists then ?
>Is browse really so bad to do nowadays ?
>
>Anybody has some thoughts on this for me ?
>
>Koos Veel.
All are good as Ed said. There is ingrid.vcx (ingrid.zip in files section) for a replacement of jkey and listboxes are not as flexible as grids. Browse on the other hand is not so bad and it has the PEM of grid now. Instead of radiobuttons, header click could be used to change order (and desc - asc as well). My preference is grids (at least it has headers where listbox doesn't). Listbox support images but just in theory with large lists.
Cetin