Click above to get retro games delivered to your door ever month!

N_XDELSKIP()
Force RaSQL to make the next record current after DELETE()

Syntax
N_XDELSKIP([<lSkip>])

Argument
default at program startup) directs RaSQL to not skip to the next record 
after a delete operation.

Returns
A logical value indicating the current setting.

Remarks
Specifying N_XDELSKIP(.F.) will make RaSQL/B act more like DBFNTX:  after a 
delete operation, the record pointer remains positioned on the current 
record.  However, since a Btrieve delete is a "true" delete, there is no 
longer a "current" record.   Any attempt to access the deleted record may 
generate an error message. In order to avoid the error message, you may want 
to issue SKIP or SKIP 1 immediately after the delete operation to position 
on a valid record.

Alternatively,  you can force RaSQL to make the NEXT logical record current 
after a delete operation by issuing function N_XDELSKIP(.T.) or command SET 
DELETESKIP ON. However, the commands DELETE WHILE or DELETE FOR may not work 
properly in this case.

This function has no effect if you are using simulated delete flags. In this 
case, the record does not actually get deleted but only gets flagged as 
deleted. The newly flagged record remains current.  See "Simulated Delete 
Flags" in the chapter "Using the Replaceable Database Driver."

Example
N_XDELSKIP(.F.)
N_XDELETE()       // No current record
N_XSKIP()         // Next record becomes current

N_XDELSKIP(.T.)
N_XDELETE()       // Next record becomes current