home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!almserv!mimas!g9utxu
- From: g9utxu@fnma.COM (Tanin Uthayanaka)
- Subject: Re: Clipper...Set Unique On/Off
- Message-ID: <1992Dec17.142157.6420@almserv.uucp>
- Sender: usenet@almserv.uucp
- Nntp-Posting-Host: mimas
- Reply-To: g9utxu@fnma.COM
- Organization: Fannie Mae
- References: <18587@mindlink.bc.ca>
- Date: Thu, 17 Dec 1992 14:21:57 GMT
- Lines: 35
-
- In article 18587@mindlink.bc.ca, John_Carson@mindlink.bc.ca (John Carson) writes:
- >It has come to my attention on a client program that SET UNIQUE ON/OFF can be
- >the start of corrupted index files. I assume that if you SET UNIQUE once with
- >the database you must all the time. If at some location in the .PRG'S it
- >isn't....trouble begins. I have not searched this out yet but will be
- >checking into it today.
- >
- >Has anyone else had this problem?
- >
- >What pseudo code do you suggest do to solve duplicate records without using
- >this SET UNIQUE ON/OFF.
- >
- >John
- >
- >--
- >>>>>>>>>>>>>>>>>>>> John_Carson@MINDLINK.BC.CA <<<<<<<<<<<<<<<<<<<<<
- >>> D.John Carson J & H Concepts (604)589-5118 <<
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
-
- John,
-
- If you are saying that some location in your .PRG is not setting unique on,
- then why don't you modify that .PRG (if you know which .PRG) to check for set unique
- (i.e. lUnique:=SET(_SET_UNIQUE)) and reset it. But if you do need to set unique off,
- that should not cause any problems either because all set unique does is modify the
- index header file at location 277 to 1.
-
- Now...if you want to simulate a set unique, you could probably do so with
- #command SKIP (your user define statement). You may also need to modify other
- clipper commands (i.e. INDEX ON) to simulate SET UNIQUE.
-
- Hope this helps.
-
- Tanin
-
-