Delete command...

[Jay R. Ashworth]

On Wed, Jul 07, 2004 at 10:23:44AM -0400, Nancy Palmquist wrote:
> Kenneth Brody wrote:
> > Nancy Palmquist wrote:
> > [...]
> > > DELETE is a peculiar as far as commands go.  It is not executed at the
> > > time it is issued.  It is held in reserve and when you finally do an END
> > > or ESCAPE or whatever makes the end of the record processing happen and
> > > you are about to go to the next record, then the DELETE is done.
> > >
> > > So you could put DELETE on line 1, continue to process for 400 lines and
> > > when it got to the END of your logic, then the record is DELETED, not
> > > before.
> > [...]
> > 
> > Just to further clarify, this applies to DELETE by itself (ie: delete the
> > current record, which you are currently in the middle of updating) as
> > opposed to "DELETE lookupname", which will delete the lookup record as
> > soon as it's executed.
> 
> Thank you Ken,  You are absolutely right and I had forgotten to qualify
> my answer completely.  

All of which folo traffic leads to a next question: after you've
DELETEd a record, further modification to the fields in that record are
no-ops.  Does filePro complain?  Should it?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	"You know: I'm a fan of photosynthesis as much as the next guy,
	but if God merely wanted us to smell the flowers, he wouldn't 
	have invented a 3GHz microprocessor and a 3D graphics board."
					-- Luke Girardi