Hi Jeff

If you're interested, we could experiment with trying to replicate your interface while using SQL "on the fly".

>Thanks, to everyone who replied.
>
>It's sad to hear that the grid control is broken in that it still can't perform rushmore optimized filtering. I should probably expand more on what my application is doing...
>
>I have a number of forms that have up to 6 grid controls on it. Prior to running the forms, I open all the required tables and apply a set relation to join the tables. Then, each grid control uses the alias of the tables as the recordsource. As the user navigates the focus on records in the parent data windows, then the children are instantly brought into focus with the associated data. Some of my forms have the largest tables as children of other tables, and some of them have the largest tables as the top level parent window. This approach has worked very well now in this application for 10 years now, and the users very quickly learn the relationships of all the tables and can find and view exactly what data they need to see. Then, users with edit priviliges can also very quickly locate the data they need to edit, and the grid controls have code behind them to log the edits into a history file. This single feature of my application has made it stand out from the competition
>that doesn't have anything even close to this interface.
>
>I have a feeling that if I substitute any "on the fly" SQL queries instead of the bound tables with the set relations, it will appear sluggish to the users.
>
>Years ago, I actually had nearly the same user interface using just multiple browse screens running on top of a foundation read. Unfortunately, I tore my hair out solving some control issues moving the focus from data window to window, and had trouble getting the history file to work. Therefore, even though this has the potiential of solving my filtering issue using the BROWSE FOR .... approach, I will probably never go back to this approach.
>
>Anyway, if anyone from Microsoft is listening, please add the equivalent of browse for table.field = "xyz" into Europa's grid control that retains rushmore performance.
>
>Thanks,
>Jeff