Dumping by RECID is possible. There are pros & cons:
useful when the db is damaged and you cannot traverse indexes
useful if you want to avoid IO on indexes which might sometimes be faster
not exactly intuitive
if the rows per block badly mismatches the data you will do lots of...
Rob's questions are great too.
To elaborate on my original answer:
/* this part is just for giggles
function numRows returns int64 ( input tblName as character ):
define variable i as int64 no-undo.
define variable b as handle no-undo.
define variable q as handle...
A BUFFER is a pointer to a single record. It is not the result set from a QUERY. To filter your results you need to focus on writing a WHERE clause that selects the records you want. There is no post-processing to remove records from a QUERY result set.
You seem to be comfortable with a...
So the fields are actually mstr_nbr and mstr_status?
Then it should be possible to take the most recent version of the revised query, without the temp-table, and run it. And that code ought to perform quite a bit better at the task that you have shown us - namely counting up the total of...
This is where things are with the code I have suggested over on StackOverflow:
define temp-table tt_mstr
field mstr_nbr as integer /* or whatever the proper data type is */
index mstr_nbr-idx is primary unique /* I am assuming mstr_nbr is unique */
for each mstr...
I'm sorry but you are making it really difficult by trickling out partial information and making apparently conflicting claims about your configuration.
If your database is a Progress database you do not need QUERY-TUNING and information about SQL Server drivers is a distraction.
On the other...