RE: Native Delete vs. SQL

I could perform READE on the files and delete Records, but would
performance be better or worse if I ran the deletes via SQL 

This is one of those cases where I don't even think Joe would
disagree... Deleting a "set" of records from a table based on key is
always going to be faster in SQL than in a loop with READE/DELETE.
HOWEVER, I assume this is a batch process, and it's probably unlikely
you'll have to do the deletes (95% it's ok?) so do you really care about
performance? If you're a shop that regularly uses SQL and everyone is
familiar w/it by all means use it. But I don't know that I'd bring it
into a shop just for this reason -- may make maintenance more difficult
down the line if all the other programmers are used to READE/DELETE.

As for Rob's question about commitment control... CC would be nice here,
but I don't think it's really needed. There is a simple, clean way to
remove unwanted rows, and I assume you don't need to hold the locks, so
it may make more sense to do it w/out CC and just delete the bad rows.

-Walden