Terry --

Thanks for your response. I had seen some references in listviews in this forum, and wondered if I should consider using them instead of grids. I can't see that there's any reason (so far, that is) for me to do so.

Your message seemed rather rah-rah for listviews, so I think I'll explain a little:

My applications are in fact designed for analysts to quickly assess data sets, and, as you said, grids are great for doing exactly that. I've already got column sorting for all columns (with extra features on top of that), and speed and multiple selects are not of much importance. Platform independence isn't much of an issue when you work for a really small organization ...

As for listviews being sexy, I don't know much about that. My organization is so low-tech that they're willing to be satisfied by applications that help them run their business more efficiently.

Cheers,

Jim


>>Briefly, what is the difference in functionality between a listview and a grid? What would I gain or lose by using listviews instead of grids?
>>
>>Thanks
>
>List views are cached - that means they're fast cause everything is in memory. List views also have column sorting (for every column) and no index required.
>
>Listviews alos have a realtime slider - grids are snap to!
>
>List views have multiple selects.
>
>lIst views have keys.
>
>
>List views are sexy.
>
>List views are OCX (less plateform dependent).
>
>With OCX you can have all your OCX navigators/listers flow through a single "node click" method - great for synchronizing modeless GUIs.
>
>
>Grids are great for "analysts" that use VFP to (quickly) assess data sets.
>
>Grids are really just browse windows with settings!
>
>Girls prefer guys that code listviews over grid heads 10 to 1~:-)