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


How very convoluted and 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. I'd rather the program generated an error.

And the .t. = vplAllApps) looks dyslexic. I'm aware that this is just me being anal, but I would put vplAllApps = .t.. No real difference.

>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.