But...you may not experience much of a gain, and in some circumstances may actually hinder performance (I'm drawing more on my SQL Server experience here, but I believe the same is true of VFP).
Logical fields have low selectivity, meaning that there are very few (two, in this case) different values.
You should run some before-and-after tests with your anticipated row counts to see if you get a gain in performance. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=
Microsoft recommends, however, to index all tables by 'Deleted()' function for better performance when SET DELETED ON.
RUSHMORE optimization is not only based on selectivity. When you select many rows in query, such logical indexes may help a lot.
[sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]
You create an index just like Chris indicates above. Of course if by 'recordset' you mean a view or cursor, you can't create an index. But you can use an ORDER BY clause in the SQL used to produce much the same effect.
1. myDBF = SYS(3)
Let us say the record set you created is a table (myDBF)
INDEX ON myField TO TAG myField
This line will create the index tag for your myField as (myDBF).CDX
2. If you want an IDX file
INDEX ON myField TO idxFileName
SET INDEX TO idxFileNAME
Hope this helps you ramani :-9
(Subramanian.G),FoxAcc, ramani_g@yahoo.com
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.