>>>May I ask WHY you have chosen to use a table exclusive? Zapping on a regular basis sounds like a bad choice, why don't you use a cursor instead? In "my book", zap is a command that should only be used maximum once or twice per year, in a specially designed table maintenance module. If ever..., I haven't used zap since the last millennium, actually I can't remember ever having used it. It's on my "commands to avoid" list, which also includes Insert. Unless by Insert you mean the SQL version, Insert in VFP comes in two completely different flavors.
>>
>>INSERT you can't avoid if you use the report builder. Since the FRX (all table based code) depends on the order of the records, it works with INSERT BLANK and INSERT BEFORE BLANK. Shudder.
>
>I never create any reports "by hand", so I don't care how VFP works internally. :-)

I once added functionality to the interface and stumbled over this. It was awkward. And I have some odd reports where fields are hidden in the band area, hard to reach by the interface, so sometimes it's more easy to use the frx to change stuff. And if I need to add a record - INSERT it must be, or I must tricky rewrite the whole frx. It feels very strange all the time.