BUG: Scrolling in a grid may be slow if you use a filtered cursor in Visual FoxPro for Windows (174584)

The information in this article applies to:

This article was previously published under Q174584

SYMPTOMS

Scrolling in a grid might be slow if the RecordSource of the grid points to a cursor, which actually is a filter of the table.

Use the following steps to work around the problem:

Use the SET KEY TO command to filter the data instead of using a SELECT-SQL command.

For example if you wanted to find all the records that have CA for the region field, use the following code:
```
      SET ORDER TO xregion
      SET KEY TO "CA"
						
```
This is assuming that there is a index tag on the region field called "xregion."
Use the NOFILTER clause in the SELECT-SQL statement to ensure that the cursor created will not be a filter. This clause is only valid in Visual FoxPro 5.0. In Visual FoxPro 3.0 you can add a ".T." to the field list to prevent the filter. For example:
```
      SELECT *,.t. FROM Customer WHERE country = "USA" INTO CURSOR test
						
```

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

This problem occurs only with cursors created with the SQL SELECT command. A local view will not create a filtered cursor.

Create a simple SELECT-SQL statement such as the following:

      SELECT * FROM Customer WHERE country = "USA" INTO CURSOR test

Modification Type:	Major	Last Reviewed:	3/11/2005
Keywords:	kbprb KB174584