Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!tate!tomr
From: tomr@dbase.a-t.com (Tom Rombouts)
Newsgroups: comp.databases
Subject: Re: DBASE IV for Sun 4 questions (long)
Message-ID: <1991Jun24.180717.12998@dbase.a-t.com>
Date: 24 Jun 91 18:07:17 GMT
References: <8331@einstein> <209@ahmcs.uucp>
Sender: news@tate.a-t.com
Organization: Ashton-Tate, Inc.
Lines: 26
Originator: tomr@dbase
Nntp-Posting-Host: dbase

In article <209@ahmcs.uucp> alan@ahmcs.uucp (Alan Mintz) writes:
>In article <8331@einstein>, banner@einstein ( infotech) writes:
>
>$         -use a different database with a like structure
>$         -append from your first database
>$         -all records from the first database will appended _including_ the 
>$         ones that were marked for deletion...
>
>I could not duplicate this under VMS, for what that is worth. Sounds like a
>pretty serious problem!

My apologies for the bandwidth if this seems too obvious, but APPEND FROM
(as well as COPY TO and others) are affected by the SET DELETED value.
To cite the doc (which, in theory, should be the same for DOS, VMS, UNIX,
etc.):

  "Records marked for deletion _are_ appended and not marked for
   deletion in the active database if SET DELETED is OFF.  If
   SET DELETED is ON, only records not marked for deletion are
   appended."

Note also that you cound add a FOR .NOT. DELETED(<source alias>)
clause to APPEND FROM to make this more explicit.


Tom Rombouts  Torrance 'Tater  tomr@ashtate.A-T.com