Sorry, I'm not a PUTM, so I can't check out message 35019 unless I stumble across it later. IAC, I do think view is the best solution for you. If your view is fairly simple, you can use the View Designer. In the filter clause, add a condition that's something like [field name] = ?[variable]. When you add the view to the DE of the form, make sure you set the NoDataOnLoad property to .T., The [variable] in the example above should be a form property, which you can then initialize to the value you want to filter by, and REQUERY() the view. If you need more details, let me know.

>Barbara...
>
>I got the LOCATE to work - the GOTO TOP blanked out the data in the grid. As for the optimizable option, well
>I stumbled on using the FILTER in the DE cursor to control what was in my grid. Any other suggestions or
>help about using views instead? (see message #350219)
>
>Thanks
>
>
>
>
>>First, I'd like to warn you that filtered grids are not optimizable, so the odds of it being slow are very high.
>>
>>To get to the top, you can either GOTO TOP or LOCATE. Normally, I'd advise against using GOTO TOP because it's not optimizable and LOCATE is, but since you're already not optimizable, it doesn't matter.
>>
>>>Is there a command to move to the top record in a grid with a filter set? I have a grid on a file
>>>and was able to limit what is displayed by using a filter in the table in the DE. When I switch
>>>the "controlling combos", a grdTally.refresh, causes the grid to redisplay except the cursor is
>>>at the LAST record in the grid. I need to get to the top record.