I would guess that the same query on a relatively small table, would show the same behavior on fifferent machines. I don't know if there is a general rule for when VFP will create a cursor, and when it will simply use the table again and add a filter to make you think it's a real cursor. A good example of how important it can be to include the NOFILTER, is when you divide a select statement into two or more lines.

Select * from table1 into cursor dummy where condition1
Select * from dummy into cursor dummy2 where condition2

In this example you would expect to see the same result as if you had only one line

Select * from table1 into cursor dummy2 where condition1 and condition2

But the result you get is the same as this line

Select * from table1 into cursor dummy2 where condition2

Adding NOFILTER after the first select statement would give you the expected result.


>Hi Tore,
>
>Thanks for the response. I see your point, but why doesn't this behavior show itself on other machines?
>
>Using the same SQL statement and performing the same changes to the same field on the report table, the query browse window does not change to the new value entered into the report table on my pc. Or others in the group for that matter. Is there a setting to control this?
>
>I failed to mention in my original post that the source table, report, is a free table.
>
>Still puzzled.
>
>Thanks again.