Delete records - inconsistent behaviour

[IdealData]

Well I only just noticed this but there's a difference between

Delete record

Delete Found records

Delete All records

Delete record deletes the current record and leaves the current found set without the record just deleted (obvious).

However, Delete Found/All records does not leave you with the current found set with the (just) deleted records - it leaves you with a found set consisting of all REMAINING RECORDS in the file.

Beware, if you are scripting then the next script step could behave differently to the way you might see it.

[mr_vodka]

Hey Ideal,

I guess it would make sense to me. If all the records are deleted from the found set, there is no found set anymore. Did you want a found set of 0 records or something?

[IdealData]

The conundrum comes when you have only 1 record in the found set. Delete CURRENT will yield 0 records, however delete FOUND/ALL will yield all remaining records - yet you only deleted 1 record.

So if you had a script that did deletions you cannot get a consistent result when there's only 1 record in the found set and you are using delete CURRENT.