Difference between revisions of "SET ORDER"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Purpose== | ==Purpose== | ||
Select the master index file from the active index file list | Select the master index file from the active index file list | ||
| Line 11: | Line 4: | ||
==Syntax== | ==Syntax== | ||
| − | SET ORDER TO <expN> | [TAG] <tag-name> [OF <.dbx filename>] | <single index filename> | + | SET ORDER TO [<expN> | [TAG] <tag-name> [OF <.dbx filename>] | <single index filename> [ASCENDING | DESCENDING]] |
| − | [ASCENDING | DESCENDING] | + | |
==See Also== | ==See Also== | ||
| − | INDEX, | + | [[INDEX]], [[INDEXKEY()]], [[INDEXORDER()]], [[MDX()]], [[NDX()]], [[SET COMPATIBLE]], [[SET INDEX]], [[TAG()]], [[TAGCOUNT()]], [[TAGNO()]], [[USE]] |
| Line 24: | Line 16: | ||
The SET ORDER TO 0 or SET ORDER TO commands cause index files to be ignored when retrieving records, but they will still be updated if any changes are made to the table. The SET ORDER TO command is only valid with tables that have index files associated with them. | The SET ORDER TO 0 or SET ORDER TO commands cause index files to be ignored when retrieving records, but they will still be updated if any changes are made to the table. The SET ORDER TO command is only valid with tables that have index files associated with them. | ||
| − | ASCENDING | DESCENDING | + | ====ASCENDING | DESCENDING==== |
The optional ASCENDING | DESCENDING can be used to determine the order in which records are accessed and displayed. | The optional ASCENDING | DESCENDING can be used to determine the order in which records are accessed and displayed. | ||
==Example== | ==Example== | ||
| − | < | + | <code lang="recital"> |
use patrons index address.dbx | use patrons index address.dbx | ||
| − | set order to tag zip of address</ | + | set order to tag zip of address |
| + | </code> | ||
==Products== | ==Products== | ||
| − | Recital | + | Recital Server, Recital |
| + | [[Category:Documentation]] | ||
| + | [[Category:Commands]] | ||
| + | [[Category:Set_Commands|ORDER]] | ||
| + | [[Category:Indexing]] | ||
| + | [[Category:Indexing Set Commands]] | ||
Latest revision as of 15:36, 13 June 2011
Contents
Purpose
Select the master index file from the active index file list
Syntax
SET ORDER TO [<expN> | [TAG] <tag-name> [OF <.dbx filename>] | <single index filename> [ASCENDING | DESCENDING]]
See Also
INDEX, INDEXKEY(), INDEXORDER(), MDX(), NDX(), SET COMPATIBLE, SET INDEX, TAG(), TAGCOUNT(), TAGNO(), USE
Description
The SET ORDER TO <expN> command selects an open index file as the master index. The master index is the index file searched during the FIND and SEEK commands, and also defines the order in which records are retrieved from the table. The master index may be selected with a number, <expN>. This is the sequential number of the index in the current list of indexes associated with a .dbf file. Single index files (.ndx/.idx) may also be selected by name, <single index filename> if SET COMPATIBLE is set to FOXPRO, FOXPLUS, FOXBASE or VFP. If .dbx files are in use, the master index may be selected using a tag name. If there are tags that have the same name, they may be specified exactly with the OF <.dbx filename> qualifier.
The SET ORDER TO 0 or SET ORDER TO commands cause index files to be ignored when retrieving records, but they will still be updated if any changes are made to the table. The SET ORDER TO command is only valid with tables that have index files associated with them.
ASCENDING | DESCENDING
The optional ASCENDING | DESCENDING can be used to determine the order in which records are accessed and displayed.
Example
use patrons index address.dbx set order to tag zip of address
Products
Recital Server, Recital
