Tom,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Browse processing is great for a many things<br>
including dropping records, but as you know, not so when it comes to<br>
dropping lots and lots of records.... because it's reading every record<br>
and making a drop decision vs using an index.<br></blockquote></div><br>I have always found the "drop all before" and "drop all after" work extremely well and stops filePro from checking any more records which is why I wasn't sure why the original request wasn't done in a browse on the original data file using both these commands. It makes this sort of functionality simple, quick and clean.<br>
<br>Ken<br>