Code:
USE a.dbf
BROWSE FOR condition
is not faster than
Code:
USE a.dbf
SET FILTER TO condition
BROWSE
And likewise displaying in a Grid.
Because, as I already said on several occasions, a browse is a grid.
That also means all you read about SET FILTER making grids slow is also true for BROWSE FOR.
SET FILTER can get sluggish. I also wrote about that, many years ago. But that typically only begins with 10,000 records or more. Today it can even be better. And through the grid's optimize property a very specific optimization is also turned on for grids. By the way, it's nevertheless .F. by default.
The absoluteöy clean way is to go for a 3 tier architecture, never directly binding grids or browse to DBF files, but using updatable views or cursoradapters.
But as long as you even haven't tried to SET FILTER you're worrying at the wrong stage of your development. The recommendation still is and always will be premature optimization is hindering you to get to your goal. Bottlenecks appear at places you don't necessarily expect them.
Bye, Olaf.
Olaf Doschke Software Engineering