>As for your problem itself, try saving the record number that you are on, >step to the next record in your index, and the delete the record that you >want to remove by record number. Since you have stepped to the next >record, when you delete the previous record, you will not be forced to >eof() unless, that is, you are at eof(). I haven't tested VFP's behavior for this, but in FP you could stay at deleted record, or even go to a deleted record, regardless of set("deleted"). I've maintained a way (by backstepping record by record) to see the deleted record, in case user wanted to undelete; I've just simulated a status bar where it said "new record", "modifying", "viewing" or "viewing (deleted)" on the left, and shown the record number on the right. Now if you deleted a record in VFP, it should have maintained the old behavior, so simply staying at the deleted record should do nothing; but probably there's some Bof()/Eof() testing in nav buttons which moves off the current record, and it doesn't GO back to it, it skips back - skipping probably to something wrong at some moment. I've changed the wizard's nav button classes long ago, so I don't exactly remember how it behaved, but I seem to remember its orientation was not bulletproof.