Curtis,

>>WHERE . . .
>> AND (Applications.lpreapp = ?vplPreapp OR .T. = ?vplAllApps)
>
>
>How very convoluted

yeah, it does look convoluted...and, i'm just discovering that, even when using the view designer, it doesn't have to be that way, once it's set up (it can be the more usual ?vplAllApps = .T.).

>I don't like paramaterized SELECTs. All they do is pop up a box prompting the end-user for a value s/he hasn't got a clue about. And frequently won't tell me about till it happens 10-15 times.

Hmmmm...my parameters always exist, so my users never see the little box.


>>not sure what you mean here...I always create indexes on my listing type views that are displayed in grids, so that users can sort on various columns...how would you do that?
>
>If you've got a base table and queries are fast I'd change the order and requery. Otherwise, I'd build the index tags on the fly as requested instead of building them all ahead of time. But that all assumes that things are fast enough to support that kind of processing.

"fast" is not a word that's used a lot out here usually. so I tend to want to take the time to build the indexes on form entry and have them ready to go...but you've given me something to think about.

Thanks...J