Difference between revisions of "SET PCUNIQUE"
Yvonnemilne (Talk | contribs) |
Helengeorge (Talk | contribs) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Purpose== | ==Purpose== | ||
Cause ’unique’ indexes to be treated as they are in dBASE | Cause ’unique’ indexes to be treated as they are in dBASE | ||
| Line 29: | Line 25: | ||
==Products== | ==Products== | ||
| − | Recital | + | Recital Server, Recital |
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
[[Category:Set_Commands|PCUNIQUE]] | [[Category:Set_Commands|PCUNIQUE]] | ||
Latest revision as of 16:58, 23 November 2009
Purpose
Cause ’unique’ indexes to be treated as they are in dBASE
Syntax
SET PCUNIQUE ON | OFF | (<expL>)
See Also
APPEND, DB_FOXPLUSBUGS, DB_FOXPROKEYS, DB_SAMBA, EDITFIELD(), FILETYPE(), Function Keys, INDEXEXT(), INDEX, SET CLIPPER, SET CLIPPER5, SET COMPATIBLE, SET EDITFIELD, SET FILECASE, SET FILETYPE, SET INDEXEXT, SET MEMOEXT, SET PCEXACT, SET PCFILTER, SET PCGRAPHICS, SET PCKEYS, SET PCLOCKING, SET PCPICTURE, SET PCSAYS, SET UNIQUE, UNIQUE()
Description
The SET PCUNIQUE command causes unique indexes to be treated in the same manner as dBASE. When PCUNIQUE is set ON, it ’hides’ records with the same key value in the UNIQUE index file. Duplicate records can be added to the UNIQUE index file but will not be displayed. However, the GOTO command will still position the record pointer on the record.
When SET PCUNIQUE is OFF, duplicate records cannot be entered into the UNIQUE index file. If the attempt is made from the FORMS system, an error message is displayed, and a new index key can be entered, or the [ABANDON] key pressed. If the attempt is made elsewhere, then an error is returned. The default for PCUNIQUE is OFF.
Example
set pcunique on append from temp
Products
Recital Server, Recital
